[go-nuts] Re: strange stack trace when panic

awsome 在 2017年6月7日星期三 UTC+8下午4:25:35，Dave Cheney写道： > > Try building your program with -gcflags="-l" to disable inlining. If that > restores the stacktrace, then it's inlining. The good news is this should > be fixed with Go 1.9 > > On Wednesday, 7 June 2017 16:37:26 UTC+10, winlin wrote: >> >>

[go-nuts] Re: strange stack trace when panic

When I run with -gcflags="-l", it works~ winlin$ go run -gcflags="-l" t.go panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x104bf82] goroutine 1 [running]: main.causedPanic() /Users/winlin/git/t.go:13

[go-nuts] Re: strange stack trace when panic

Try building your program with -gcflags="-l" to disable inlining. If that restores the stacktrace, then it's inlining. The good news is this should be fixed with Go 1.9 On Wednesday, 7 June 2017 16:37:26 UTC+10, winlin wrote: > > Hi, I'm confused by the stack trace when panic, and I have