-
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
runtime: "traceback stuck" during TestTraceCPUProfile #52829
Comments
(CC @golang/runtime) |
Also seen in https://storage.googleapis.com/go-build-log/12336990/linux-arm-aws_075a22d5.log (a TryBot run). |
Thanks. I'll take a look. |
Here's another TryBot example: https://storage.googleapis.com/go-build-log/c3bb95e0/linux-arm-aws_76aa21f5.log |
I think the signal PC is
At that very instruction, PC=LR. That call is injected by the assembler at https://cs.opensource.google/go/go/+/master:src/cmd/internal/obj/arm/obj5.go;l=69 I'll see if we can make |
Change https://go.dev/cl/405482 mentions this issue: |
Looking over the failures for #52693, I see a new variety that also doesn't match #52764.
In this crash,
runtime.gentraceback
as called fromruntime.sigprof
complains of "fatal error: traceback stuck". The failure is on 32-bit linux/arm. That assertion is new in 74f0009, for #52116. CC @cherrymuiBoth the assertion in gentraceback and the test that triggered the crash are new in the Go 1.19 cycle, which I think makes this a release blocker. CC @bcmills
greplogs -dashboard -l -e 'traceback stuck' --since=2022-04-01 -md
2022-05-10T14:22:16-59ef3a9/linux-arm-aws
The text was updated successfully, but these errors were encountered: