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

Allocate guard page under existing stack, not in it #22

Closed
wants to merge 2 commits into from
Closed

Allocate guard page under existing stack, not in it #22

wants to merge 2 commits into from

Conversation

whitequark
Copy link
Contributor

This fixes a segfault when the allocated stack is just one page long, and adds a test. Allocating a stack one page long was legal according to the documentation and it would be accessible, but what happened is a stack one page long was allocated and that one page was marked as guard page (instead of one page under the entire useful stack area).

This also refactors the fringe::os module to use Result consistently.

@whitequark whitequark changed the title Allocate guard page under existing stack, not in it. Allocate guard page under existing stack, not in it Jul 17, 2016
This fixes a segfault when the allocated stack is just one page long.

This also refactors the fringe::os module to use Result consistently.
@edef1c edef1c closed this in 9734c3d Jul 17, 2016
edef1c pushed a commit that referenced this pull request Feb 25, 2017
This fixes a segfault when the allocated stack is just one page long.

This also refactors the fringe::os module to use Result consistently.

close #22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant