Michael Pratt

To summarize: * Go uses small goroutines stacks, so there is no guarantee that there is enough space on the stack for signal context and frame at all times. *...

Ah, it turns out this is a duplicate of #39857, which has been discussed at some length but not resolved.

Given that you commented on #52116, I assume that this application was also suffering from that bug before this (seemingly incomplete) fix?

We have special cases for morestack and systemstack [here](https://cs.opensource.google/go/go/+/master:src/runtime/traceback.go;l=168;drc=bd302502d39b6172bf3db6abfa49fdcaa124ee50), but I don't believe they are relevant because (a) `funcID_morestack` only applies to `morestack`, not `morestack_noctxt`, and (b) we should only...

If you are willing to patch the runtime, there are a few changes that would be helpful. * https://go.dev/cl/424195: This just expands the stack dump to include the entire stack,...

> There's some slew since 1.18.5: Oops, apologies, I made this CL based on tip rather than 1.18. Did you get this fixed? If not I can provide another on...

Yes, `go install` accepts tags. I also see that the stack dump doesn't include the entire stack either (https://go.dev/cl/424195). I'd guess that your build isn't picking up the patches to...

Thanks. By the way, do you happen to be using musl libc (/Alpine Linux)? (Is this even a cgo binary?) I'm investigating #54306 in parallel, presumably an issue with musl....

Thanks, I'll take a look! Does this one have debuglog output at the end? (Lots of lines mostly containing `gentrace: ...`)

Hrm, that is quite frustrating. What I can tell from the stack dump is that the SP/FP we've landed at is certainly not a valid frame pointer. It is hard...