runtime: stack should indicate when stack frames are omitted

[rogpeppe]

What version of Go are you using (go version)?

$ go version
go version devel go1.19-2bea43b0e7 Thu May 12 04:47:29 2022 +0000 linux/amd64

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.go that 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 tracebacklimit setting inside $GODEBUG for example).

[randall77]

I was hoping one day we would fix #7181 and maybe cure this one as a side effect.

[seankhliao]

dup of #32383 ?

[rogpeppe]

@seankhliao Indeed so - I searched but didn't find that.
@randall77 Yes, that would be great! (especially if that allowed runtime configuration of the number of frames to show).

I'll close this as a dupe of #32383.