You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2020. It is now read-only.
It would be really great if we could come up with some way to allocate a guard page on the stack without a hard dependency on system APIs. For example, on *nix systems we have mprotect(). But in other contexts we need other things. In a kernel context, there will be some internal API that will be used. So this methodology needs to be pluggable.
This also raises the question of the wisdom of passing the stack as a slice. Hopefully, someone will review and comment on that.
The text was updated successfully, but these errors were encountered:
It would be really great if we could come up with some way to allocate a guard page on the stack without a hard dependency on system APIs. For example, on *nix systems we have
mprotect()
. But in other contexts we need other things. In a kernel context, there will be some internal API that will be used. So this methodology needs to be pluggable.This also raises the question of the wisdom of passing the stack as a slice. Hopefully, someone will review and comment on that.
The text was updated successfully, but these errors were encountered: