panicparse
delve
Our great sponsors
| panicparse | delve | |
|---|---|---|
| 3 | 52 | |
| 3,480 | 22,012 | |
| - | 1.0% | |
| 0.0 | 9.2 | |
| 7 months ago | 1 day ago | |
| Go | Go | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
panicparse
-
how to demangle a Golang crash call stack
Maybe using panicparse helps you understanding the stack traces.
-
Uhoh
We have a similar internal package where we can add per stack variables / context. We use https://github.com/maruel/panicparse to get a structured stacktrace, then append to that, and the whole json blob ships to Sentry. I think it's awesome and has almost completely eliminated any need for logging.
-
Remove source path from Go's panic stack trace
This one works nicely too: https://github.com/maruel/panicparse
delve
-
The worst thing about Jenkins is that it works
At a recent job, we had slightly different containers for local dev; our backend containers (for a Go app) had Air [1] installed for live reloading, plus Delve [2] running inside the container for VS Code's debugger to connect to. We also had a frontend container for local dev, which didn't get deployed as a container, just as static files.
-
Delve v1.21.2 is out now
https://github.com/go-delve/delve/releases/tag/v1.21.2 Thanks Derek and the rest of the team for helping us to debug in a normal way!
- I do not use a debugger
-
Writing and debugging integration tests of multiple processes with Golang
My employer has a commercial solution for this but Delve does supports `rr` traces natively for this purpose, which gives a complete open-source solution (https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_replay.md).
- No support for debugging Go on OpenBSD
- Delve v1.20.2 is out now
-
Tools besides Go for a newbie
delve and related IDE integrations
-
What a good debugger can do
For time travel debugging in Go:
The Delve debugger for Go supports debugging rr traces: https://github.com/go-delve/delve/blob/master/Documentation/...
Undo (who I work for) maintain a fork that debugs our LiveRecorder recordings: https://docs.undo.io/GoDelve.html
Either rr (https://rr-project.org/) or our UDB debugger (https://undo.io/solutions/products/udb/) can do some time travel debugging of Go programs via GDB's built-in support for Go. I believe its weakness is in support for goroutines, since they don't map well onto its idea of how programs run.
-
Is there a neovim config with preconfigured debugger?
So in my case I use https://github.com/leoluz/nvim-dap-go (which itself calls out to the CLI tool https://github.com/go-delve/delve).
-
What's wrong with my GoLand debugger?
Clone https://github.com/go-delve/delve.git
What are some alternatives?
excelize - Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
air - ☁️ Live reload for Go apps
godropbox - Common libraries for writing Go services/applications.
go-debug
go-torch
vim-go - Go development plugin for Vim
Task - A task runner / simpler Make alternative written in Go
gorequest - GoRequest -- Simplified HTTP client ( inspired by nodejs SuperAgent )
ngrok - Unified ingress for developers
go-sitemap-generator - go-sitemap-generator is the easiest way to generate Sitemaps in Go
hub - A command-line tool that makes git easier to use with GitHub.
gohper