Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GENERATED_KERNEL_OBJECT_FILES end up in application memory #4001

Closed
zephyrbot opened this issue Aug 24, 2017 · 3 comments
Closed

GENERATED_KERNEL_OBJECT_FILES end up in application memory #4001

zephyrbot opened this issue Aug 24, 2017 · 3 comments
Assignees
Labels
area: Kernel area: Memory Protection bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Milestone

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Aug 24, 2017

Reported by Andrew Boie:

Objects in GENERATED_KERNEL_OBJECT_FILES, if they are not in custom section, end up in application memory space if CONFIG_APPLICATION_MEMORY is turned on.

Fix this so that the objects are rolled into libzephyr.a.

(Imported from Jira ZEP-2571)

@zephyrbot zephyrbot added priority: low Low impact/importance bug area: Kernel bug The issue is a bug, or the PR is fixing a bug labels Sep 23, 2017
@zephyrbot zephyrbot added this to the v1.10.0 milestone Sep 23, 2017
@andrewboie
Copy link
Contributor

need to check but pretty sure I fixed this

@galak
Copy link
Collaborator

galak commented Nov 9, 2017

@andrewboie can you check and close it out if fixed.

@galak
Copy link
Collaborator

galak commented Nov 28, 2017

@andrewboie ping on closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Kernel area: Memory Protection bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants