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.

Sign up for GitHub

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

Jump to bottom

Test framework aliases MappedMemoryRegion #53

Open
mullr opened this issue Aug 14, 2019 · 0 comments
Open

Test framework aliases MappedMemoryRegion #53

mullr opened this issue Aug 14, 2019 · 0 comments

Comments

@mullr
Copy link
Collaborator

mullr commented Aug 14, 2019

It reuses the same one each time, and then breaks lifetime rules by aliasing it and letting the alias be consumed. This is a problem because this memory is used for stack setup, and we'd like to unmap the setup pages after it's done, but doing so breaks the tests.
mullr added a commit that referenced this issue Aug 14, 2019
@mullr
Manually flush stack pages after populating them
f33e339 
We'd prefer to unmap the pages, but we can't (See #53). Instead directly flush
them, to be sure the stack is visible in the target process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mullr