123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960 |
- .\"Created with GNOME Manpages Editor Wizard
- .\"http://sourceforge.net/projects/gmanedit2
- .TH panicparse 1 "February 18, 2019" "" "/usr/bin/panicparse"
- .SH NAME
- /usr/bin/panicparse \- program for parsing go stack traces
- .SH SYNOPSIS
- .B panicparse
- .RI [ options ]
- .br
- .SH DESCRIPTION
- .B panicparse
- Parses panic stack traces, densifies and deduplicates goroutines with similar stack traces. It helps debugging crashes and deadlocks in heavily parallelized process. panicparse helps make sense of Go crash dumps. Merely pipe in a crash stack trace from a go program. If you need one to get an idea, use panic(1) to create one.
- .SH OPTIONS
- .B
- .IP -aggressive
- Aggressive deduplication including non pointers
- .IP -f
- usage: -f string
- Regexp to filter out headers that match, ex: -f 'IO wait|syscall'
- .IP -force-color
- Forcibly enable coloring when with stdout is redirected
- .IP -full-path
- Print full sources path
- .IP -html
- usage: -html string
- Output an HTML file
- .IP -m
- usage: -m string
- Regexp to filter by only headers that match, ex: -m 'semacquire'
- .IP -no-color
- Disable coloring
- .IP -parse
- Parses source files to deduct types; use -parse=false to work around bugs in source parser (default true)
- .IP -rebase
- Guess GOROOT and GOPATH (default true)
- .IP -v
- Enables verbose logging output
- .SH EXAMPLES
- .B template
- (panicing_program) |& pp
- .B test
- panic int |& pp
- .SH BUGS
- For any bugs checkout upstream bug reports at https://notabug.org/themusicgod1/panicparse/issues
- .SH "SEE ALSO"
- pp(1) panic(1)
|