Pry VS delve

that's surprising considering `pry`[1] is such an amazing debugger IMO.

[1] https://github.com/pry/pry

All of my recent tutorials and projects were primarily managed using the default Ruby REPL, irb, and I must say it's been nothing short of amazing. However, what ultimately prompted me to switch to Pry was its offering of better defaults. But what exactly does that mean? Let me demonstrate:

For older versions: Pry Gem

To do that, I would install `pry` into your rails project and then use it look around right before your test fails.https://github.com/pry/pry

This means I can be editing a shell script and easily inject arbitrary regions into a shell buffer for immediate testing (point never leaves the window where I am editing, and I can view the shell output in an adjacent window). This is similar to what Robe does with Pry within an inferior Ruby process using comint.

https://pry.github.io/ - also a lot of features from Pry have made it into the default IRB these days, but I still use pry. I don't know the equivalent commands in IRB.

For debugging, while not multi-threaded, to my knowledge, is the pry gem for debugging. There are a few different flavors, for instance, my favorite is pry-byebug.

Github Link : https://github.com/pry/pry

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.

[1] https://github.com/cosmtrek/air

[2] https://github.com/go-delve/delve/

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!

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).

delve and related IDE integrations

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.

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).

Clone https://github.com/go-delve/delve.git