mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
runtime: never show system goroutines in traceback
Fixes #9791 g.issystem flag setup races with other code wherever we set it. Even if we set both in parent goroutine and in the system goroutine, it is still possible that some other goroutine crashes before the flag is set. We could pass issystem flag to newproc1, but we start all goroutines with go nowadays. Instead look at g.startpc to distinguish system goroutines (similar to topofstack). Change-Id: Ia3467968dee27fa07d9fecedd4c2b00928f26645 Reviewed-on: https://go-review.googlesource.com/4113 Reviewed-by: Keith Randall <khr@golang.org>
This commit is contained in:
parent
84e2567537
commit
59495e8dfd
9 changed files with 61 additions and 14 deletions
|
|
@ -199,7 +199,6 @@ type g struct {
|
|||
waitsince int64 // approx time when the g become blocked
|
||||
waitreason string // if status==gwaiting
|
||||
schedlink *g
|
||||
issystem bool // do not output in stack dump, ignore in deadlock detector
|
||||
preempt bool // preemption signal, duplicates stackguard0 = stackpreempt
|
||||
paniconfault bool // panic (instead of crash) on unexpected fault address
|
||||
preemptscan bool // preempted g does scan for gc
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue