diff options
| author | Russ Cox <rsc@golang.org> | 2013-09-11 11:59:19 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2013-09-11 11:59:19 -0400 |
| commit | fa4984d535b23c0d2b14650a8842d63083893af3 (patch) | |
| tree | 15b072d61bc27e6cf175524b4ada5261bf36a53b /src/pkg/runtime/panic.c | |
| parent | 382738af513a5390620b55a84b9e14f3afd0128e (diff) | |
| download | go-fa4984d535b23c0d2b14650a8842d63083893af3.tar.xz | |
runtime: show runtime.panic frame in traceback
Otherwise, if panic starts running deferred functions,
the code that panicked appears to be calling those
functions directly, which is not the case and can be
confusing.
For example:
main.Two()
/Users/rsc/x.go:12 +0x2a
runtime.panic(0x20dc0, 0x2100cc010)
/Users/rsc/g/go/src/pkg/runtime/panic.c:248 +0x106
main.One()
/Users/rsc/x.go:8 +0x55
This makes clear(er) that main.Two is being called during
a panic, not as a direct call from main.One.
Fixes #5832.
R=golang-dev, iant
CC=golang-dev
https://golang.org/cl/13302051
Diffstat (limited to 'src/pkg/runtime/panic.c')
0 files changed, 0 insertions, 0 deletions