-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/pprof: segmentation fault #10428
Comments
This is the earliest instance I was able to find: Taking a stab in the dark, I would guess this is happening in the trace verifier and that it's some assumption I broke in the commits leading up to that one. I bet this would be easy to track down if we had a stack trace for the failure, but I haven't been able to reproduce it locally (even on linux-amd64). Any idea why we're not getting a stack trace? |
Perhaps it's because GOTRACEBACK isn't set to 2 on the builders and it's the runtime itself that's crashing? |
Possibly related: various builders are sometimes failing with ''' Started around the same time. linux-386 windows-amd64-2003kardianos linux-amd64-nocgo |
Actually, I found the "failed to parse trace" failures back to 089d363, which looks likely to be related to that commit. So that's probably a red herring. |
Finally got a stack trace using gomote (yay gomote). I think I know what's wrong and I'm working on it.
|
A number of builds and trybots have failed recently with:
linux-amd64-race
:http://build.golang.org/log/60268e3ff9d00b59c53a8ab7a157f62c92a32694
http://build.golang.org/log/791514375c93966427c693becc4a52c72ae0b0a3
linux-386
:https://storage.googleapis.com/go-build-log/cd8e2e9b/linux-386_5f49e79a.log
/cc @dvyukov @rsc @aclements
The text was updated successfully, but these errors were encountered: