Parses panic stack traces, densifies and deduplicates goroutines with similar stack traces. Helps debugging crashes and deadlocks in heavily parallelized process.
panicparse helps make sense of Go crash dumps:
- >50% more compact output than original stack dump yet more readable.
- Exported symbols are bold, private symbols are darker.
- Stdlib is green, main is yellow, rest is red.
- Deduplicates redundant goroutine stacks. Useful for large server crashes.
- Arguments as pointer IDs instead of raw pointer values.
- Pushes stdlib-only stacks at the bottom to help focus on important code.
- Usable as a library!
- Warning: please pin the version (e.g. vendor it). Breaking changes are not planned but may happen.
- Parses the source files if available to augment the output.
- Works on Windows.
go get github.com/maruel/panicparse/cmd/pp
Piping a stack trace from another process
- Ubuntu (bash v4 or zsh):
- OSX, install bash 4+, then:
- Windows or OSX with stock bash v3:
- Fish shell:
go test -v |&pp
Windows or OSX native bash (which is 3.2.57): They don't have this shortcut, so use the long form:
go test -v 2>&1 | pp
Fish: It uses ^ for stderr
so the shortcut is
go test -v ^|pp
PowerShell: It has broken
2>&1 redirection. The workaround is to shell out to cmd.exe. :(
On POSIX, use
Ctrl-\ to send SIGQUIT to your process,
pp will ignore
the signal and will parse the stack trace.
Parsing from a file
To dump to a file then parse, pass the file path of a stack trace
go test 2> stack.txt pp stack.txt
Starting with Go 1.6,
single instead of
1 that was used in 1.5 and before. To get all
goroutines trace and not just the crashing one, set the environment variable:
set GOTRACEBACK=all on Windows. Probably worth to put it in your
Updating bash on OSX
If you have
You may have the Perl PAR Packager installed. Use long name
go get github.com/maruel/panicparse