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?
to your account
This CL (292558b) broke Dragonfly:
runtime: restore the Go-allocated signal stack in unminit
I emailed Austin & Ian details of how to access a VM I created.
The text was updated successfully, but these errors were encountered:
/cc @aclements @ianlancetaylor
This most likely has to do with the fact that on DragonFly a newly created thread inherits the alternate signal stack of the creating thread. See the comment in minit in runtime/os_dragonfly.go.
Sorry, I was looking at an old source tree due to a complex accident. DragonFly used to work that way, but it's been fixed.
Change https://golang.org/cl/83035 mentions this issue: runtime: don't use MAP_STACK on DragonFly in SigStack test
runtime: don't use MAP_STACK on DragonFly in SigStack test
Successfully merging a pull request may close this issue.