runtime: stack should indicate when stack frames are omitted #53349
Labels
Comments
|
I was hoping one day we would fix #7181 and maybe cure this one as a side effect. |
|
dup of #32383 ? |
|
@seankhliao Indeed so - I searched but didn't find that. I'll close this as a dupe of #32383. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
Yes.
What did you do?
https://go.dev/play/p/S-RsQFj9gL1
What did you expect to see?
I'd expect to see an indication that stack frames have been omitted from the
stack trace.
What did you see instead?
I didn't see any indication that frames were omitted, which makes it easy to misinterpret the traceback output.
There is logic inside
src/runtime/traceback.gothat seems to be intended to print "...additional frames elided..." but that logic doesn't seem to be triggered. A rough bisection through Go major versions indicates that this was broken some time between go1.7 and go1.8.As an additional consideration, it would be great if it were possible to configure the number of frames printed (for example with a
tracebacklimitsetting inside$GODEBUGfor example).The text was updated successfully, but these errors were encountered: