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
runtime: random fatal errors on iOS #14070
Comments
We can observe typically:
|
Those errors do look similar to the ones we saw on NetBSD and DragonFly. @crawshaw Is it possible for you to run this C program on Darwin/ARM, to see how signal stacks are handled for newly created threads?
|
I run the program on iOS 5.1.1 and the output is:
main 1 0x0 0x0 0x4
thread 0x0 0x0 0x4
main 2 0x0 0x0 0x4
main 3 0x33000 0x20000 0x0
thread 0x0 0x0 0x4
main 4 0x33000 0x20000 0x0
|
For a few (uninteresting) reasons it would take me a couple of hours work to run this. Hopefully the run by @minux does the job. |
The run by minux tells me that the problem on iOS is not the same as the problem on NetBSD and DragonFly. This will require more investigation. |
CL https://golang.org/cl/18940 mentions this issue. |
/cc @ianlancetaylor
According to the dashboard, the build started to fail with signal failures with a7cad52.
Before (mostly timeouts): http://build.golang.org/log/a04d0ed55471343ddd7dec8bb8ef9459cc02588e
After (signal failures): http://build.golang.org/log/32a73620035a8c1101d15bcbbdce2cdce640d70f
The text was updated successfully, but these errors were encountered: