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 at very high address on ppc64 #64290
Comments
CC @mknyszek |
Interesting, it's segfaulting on the type pointer. That pointer also doesn't look like it's nil, either, which makes this very odd. So far it looks like this has only failed on linux-ppc64? Is that right? |
@mknyszek that's the only failure I've observed, but it might be worth checking with greplogs. |
Hey @golang/ppc64, is there something special about where the type metadata (from the binary) is placed in the address space? i.e. does |
@findleyr Thanks. |
I'd err on the side of bogus. I think mapped memory usually falls below |
There was another failure, this time unrelated to typePointersOfUnchecked, with a similar segfault on a similar address. This makes me think it's more general memory corruption. https://build.golang.org/log/cbb742b677c36b578951d0a9b5589c1dc223a1c1 |
The high bit that seems to be set is the 60th bit? Why does that sound familiar... |
New segfault found in the gopls tests.
2023-11-20 18:35 linux-ppc64-sid-buildlet tools@8966034e go@ddb38c3f x/tools/gopls/internal/regtest/marker (log)
— watchflakes
Originally posted by @gopherbot in #63736 (comment)
The text was updated successfully, but these errors were encountered: