Crash your app in style (evacuated from NSA/Microsoft Github)
anonymous 1461851631 debian nitpicks | 5 years ago | |
---|---|---|
cmd | 6 years ago | |
debian | 5 years ago | |
internal | 6 years ago | |
stack | 6 years ago | |
.travis.yml | 7 years ago | |
Gopkg.lock | 6 years ago | |
Gopkg.toml | 7 years ago | |
LICENSE | 10 years ago | |
README.md | 5 years ago | |
main.go | 6 years ago | |
panic.1 | 5 years ago | |
panicparse.1 | 5 years ago | |
parse.gif | 6 years ago | |
pp.1 | 5 years ago |
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:
|&
^|
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
Fish: It uses ^ for stderr
redirection
so the shortcut is ^|
:
go test -v ^|pp
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
GOTRACEBACK
defaults to single
.
To get all goroutines trace and not just the crashing one, set the environment variable:
export GOTRACEBACK=all
Probably worth to put it in your .bashrc
.
/usr/bin/pp
installedIf you try pp
for the first time and you get:
Creating tables and indexes...
Done.
and/or
/usr/bin/pp5.18: No input files specified
you may be running the Perl PAR Packager instead of panicparse.
You have two choices, either you put $GOPATH/bin
at the begining of $PATH
or
use panicparse
instead of pp
:
go test 2> panicparse