-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: TestSegv/Segv
failure with unexpected return pc
on openbsd-386-68
#52043
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
Comments
On OpenBSD we use libc for syscalls. We generally cannot unwind the C stack if the signal arrives in the libc functions. Perhaps for short term skipping on all OpenBSD sounds reasonable. But I still don't understand why we get into sigpanic. I think we should not use sigpanic for externally-generated SIGSEGV. Maybe sigcode is not correct on OpenBSD/386? |
Only one of these this year and it's not a first-class port, and (unlike If the builder gets too noisy I'll remove it from triage, but I don't think this needs to be a release-blocker. |
OpenBSD 6.8 is no longer a supported version of OpenBSD. Our https://github.com/golang/go/wiki/MinimumRequirements documents that we only support the current stable version, which is OpenBSD 7.1. Maybe we can remove OpenBSD 6.8 builders and close this. |
Rolling forward to 1.20. Please comment if you disagree. Thanks. |
(CC @golang/runtime)
The text was updated successfully, but these errors were encountered: