Parses panic stack traces, densifies and deduplicates goroutines with similar stack traces. Helps debugging crashes and deadlocks in heavily parallelized process.
(Source)
-
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.
- Deduplicate 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!
- Works on Windows.
go get github.com/maruel/panicparse/cmd/pp
- Ubuntu (bash v4 or zsh):
|& - OSX, install bash 4+, then:
|& - Windows or OSX with stock bash v3:
2>&1 | - Fish shell:
^|
pp streams its stdin to stdout as long as it doesn't detect any panic.
panic() and Go's native deadlock detector print to
stderr via the native print()
function.
Bash v4 or zsh: |& tells the shell to redirect stderr to stdout,
it's an alias for 2>&1 | (bash
v4,
zsh):
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
redirection
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.
To dump to a file then parse, pass the file path of a stack trace
go test 2> stack.txt
pp stack.txt
(Source)
Install bash v4+ on OSX via homebrew or macports. Your future self will appreciate having done that.
You may have the Perl PAR Packager installed. Use long name panicparse then;
go get github.com/maruel/panicparse