mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
runtime: print a stack trace at "morestack on g0"
Error like "morestack on g0" is one of the errors that is very hard to debug, because often it doesn't print a useful stack trace. The runtime doesn't directly print a stack trace because it is a bad stack state to call print. Sometimes the SIGABRT may trigger a traceback, but sometimes not especially in a cgo binary. Even if it triggers a traceback it often does not include the stack trace of the bad stack. This CL makes it explicitly print a stack trace and throw. The idea is to have some space as an "emergency" crash stack. When the stack is in a really bad state, we switch to the crash stack and do a traceback. Currently only implemented on AMD64 and ARM64. TODO: also handle errors like "morestack on gsignal" and bad systemstack. Also handle other architectures. Change-Id: Ibfc397202f2bb0737c5cbe99f2763de83301c1c1 Reviewed-on: https://go-review.googlesource.com/c/go/+/419435 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Michael Pratt <mpratt@google.com>
This commit is contained in:
parent
29b80397a8
commit
0262ea1ff9
6 changed files with 147 additions and 27 deletions
|
|
@ -804,6 +804,14 @@ func TestG0StackOverflow(t *testing.T) {
|
|||
if n := strings.Count(string(out), "morestack on g0\n"); n != 1 {
|
||||
t.Fatalf("%s\n(exit status %v)", out, err)
|
||||
}
|
||||
if runtime.GOARCH == "amd64" || runtime.GOARCH == "arm64" {
|
||||
// check for a stack trace
|
||||
want := "runtime.stackOverflow"
|
||||
if n := strings.Count(string(out), want); n < 5 {
|
||||
t.Errorf("output does not contain %q at least 5 times:\n%s", want, out)
|
||||
}
|
||||
return // it's not a signal-style traceback
|
||||
}
|
||||
// Check that it's a signal-style traceback.
|
||||
if runtime.GOOS != "windows" {
|
||||
if want := "PC="; !strings.Contains(string(out), want) {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue