-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
cmd/compile: invalid memory address or nil pointer dereference in gc.convlit1 #35621
Comments
Is the failure reproducible or was it one time? I suspect runtime memory corruption if it doesn't reproduce. |
As far as I can tell, it's a one-off or just really rare. I haven't seen it since, but I haven't rebuilt the toolchain all that many times today. (I get the corruption in #35326 way more often and consistently.) |
Yeah, runtime memory corruption seems most likely to me then. The nil pointer dereference happened here: go/src/cmd/compile/internal/gc/const.go Line 246 in 72f333a
But just a few lines earlier we have: go/src/cmd/compile/internal/gc/const.go Lines 230 to 233 in 72f333a
The only intermediate code that modifies go/src/cmd/compile/internal/gc/const.go Lines 239 to 243 in 72f333a
but that just calls go/src/cmd/compile/internal/gc/subr.go Lines 387 to 390 in 72f333a
which is plainly safe. |
Yep, that's correct. I was just about to comment on your mega issue with a link here. Feel free to close this in favor of #35777 once you've gotten whatever info you wanted. |
Thanks. I've added this to the super-bug. Since this isn't reproducible, closing in favor of the super-bug. |
What version of Go are you using (
go version
)?Installing tip at 3bea90d (can't use
gotip version
because it failed to build).Does this issue reproduce with the latest release?
N/A
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Ran
gotip download
to build the latest tip.What did you expect to see?
A successful build.
What did you see instead?
Rerunning
gotip download
was successful, so I'm not sure how reproducible this is.The text was updated successfully, but these errors were encountered: