Analysis updated 2026-07-03
Pipe a crashing Go program or test run through panicparse to get a compact, grouped stack trace instead of thousands of repeated lines.
Embed the library into a Go HTTP server to expose a live endpoint showing all goroutines in a readable format for production debugging.
Save a goroutine dump to a file and pass it to panicparse to diagnose a deadlock without needing a live crash.
| maruel/panicparse | olivia-ai/olivia | nikoksr/notify | |
|---|---|---|---|
| Stars | 3,714 | 3,719 | 3,721 |
| Language | Go | Go | Go |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 3/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Panicparse is a command-line tool for Go developers that makes crash output readable. When a Go program crashes or deadlocks, the runtime prints a stack trace that can be hundreds or thousands of lines long, especially in programs that run many goroutines at the same time. Goroutines are Go's way of doing multiple things concurrently, and a busy server might have thousands of them running when it crashes. The resulting dump is technically complete but extremely hard to read. Parseparse processes that raw crash output and reformats it into something much more compact and organized. It groups goroutines that share the same stack trace so identical ones appear once with a count, rather than repeated hundreds of times. It pushes goroutines that are only running standard library code to the bottom of the output so the developer can focus on their own application code. It replaces raw memory addresses with shorter identifier labels so pointers are easier to follow. The result is described as more than 50% more compact than the original while being more readable. Usage is straightforward: you pipe the output of your Go program or test run through the tool on the command line. The exact pipe syntax varies slightly depending on whether you are on Linux, macOS, or Windows, and which shell you are using, and the README covers all the common cases. You can also dump a crash to a file and pass that file to the tool directly. Beyond the command-line formatter, the project includes a library component that can be embedded into a running Go HTTP server. This lets you add an endpoint to your server that shows a live snapshot of all goroutines in a formatted, readable layout, which is useful for diagnosing slowdowns or deadlocks in production without needing a crash dump.
A command-line tool that makes Go crash dumps readable by grouping identical goroutines and cutting output length by more than half, plus an embeddable library for live goroutine inspection in running servers.
Mainly Go. The stack also includes Go.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.