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: segfault in mallocgc (atomic.Casuintptr call in unlock) #17796
Comments
CC @alandonovan |
This is a segfault in mallocgc, not a bug in guru itself. Which revision of Go are you using exactly? Is it deterministic? |
Wow that's unsettling. I installed Go via homebrew months ago, upgraded via homebrew some weeks ago, and recently upgraded to OSX Sierra. From my shell it's consistently 1.7.3.
I agree those filenames say |
In case it helps I'm using this version of |
I wouldn't be surprised if my |
Rebuilding guru with 1.7.3 would likely make this problem disappear. However, it is a valid bug report against the Go 1.6.3. runtime's mallocgc function. |
Alright well let me know if you'd like anything else for me, otherwise I'll rebuild my guru tomorrow. |
While true, 1.6.3 is no longer supported. I did dig into this a bit in case it was something that still affected 1.7 or master. Unfortunately, it's clearly memory corruption since something overwrote the global Given all of this, I think you should go ahead and rebuild guru and I'm going to close this issue. Obviously, if it continues to happen, we can reopen it. :) |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Ran go guru via
go-guru-describe
in emacs.What did you expect to see?
not a panic
What did you see instead?
a panic
https://gist.github.com/mlsteele/caa4e523c4dc0aa77588854bc4f9f74a#file-panic-log
(sorry about the numerous edits of this post, accidentally ctrl+enter'd early)
The text was updated successfully, but these errors were encountered: