-
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/link: panic with index out of range
in cmd/link/internal/loader.(*Loader).resolve
#62355
Comments
Found new dashboard test flakes for:
2023-08-29 18:31 linux-loong64-3a5000 go@22f9e0ef cmd/link [build] (log)
|
index out of range
panics on loong64
Found new dashboard test flakes for:
2023-07-06 13:09 linux-loong64-3a5000 go@b490bdc2 archive/tar.test [build] (log)
2023-08-29 15:33 linux-loong64-3a5000 go@2efebf3e internal/coverage/slicereader.test [build] (log)
2023-08-29 16:49 linux-loong64-3a5000 go@2e644cce test.Test (log)
2023-08-29 18:28 linux-loong64-3a5000 go@208f3618 test.Test (log)
|
(attn @golang/loong64) |
Thanks!. I have tested on other machines and the error has not been reproduced. This problem and the problem described in #62336 may be caused by the memory stability of this builder. I have reproduced these two errors before on machines with memory stability bugs. I have replaced the memory module of this builder to see if these two errors still occur. At the same time, I also tested on other local machines to see if the two errors can be reproduced. |
index out of range
panics on loong64index out of range
panics on loong64
index out of range
panics on loong64index out of range
in cmd/link/internal/loader.(*Loader).resolve
This turns out not to be specific to (attn @golang/compiler for re-triage) |
Found new dashboard test flakes for:
2023-11-01 07:10 linux-ppc64-sid-buildlet go@1a58fd0f test.Test (log)
|
What version of Go do you use? I saw GOVERSION="go1.18" but I cannot reproduce it with go1.18. |
Found new dashboard test flakes for:
2024-05-13 16:40 x_telemetry-go1.21-darwin-amd64-nocgo telemetry@80019551 release-branch.go1.21@8fbd4d7b [build] (log)
|
👋 Hello, I had the same panic error in the linker, using Go 1.22.8, on It happened simultaneously on a dozen packages while running tests. Stack trace
Here is the full job log, let me know if you can't access it. Here are some info about the (Github) runner:
|
2146959359 is hex 0x7ff7ffff, which is one bit different from 0x7fffffff, which is a valid and special index (it is handled specially, instead of indexing into a slice). Maybe there is a one-bit corruption of the object file? Does the failure reproducible if you clean the build cache ( |
Sadly I can't say, the job runs in short lived Github runners so I can't check the state when it errored, and it was a one-off error we can't reproduce... For the record in my previous comment I mentioned it had happened before, but I think I found the case I had in mind and it was actually different (also linker panic on Darwin, but different cause). |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: