debugger VS delve

However, I know https://github.com/emad-elsaid/debugger has been working on a debugger frontend, I don't think it has the side-by-side view yet. And... there's another frontend https://github.com/aarzilli/gdlv as well.

https://github.com/emad-elsaid/debugger Is a golang debugger gui that itself is written in golang.

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

git clone https://github.com/go-delve/delve cd delve go install github.com/go-delve/delve/cmd/dlv

| Language | Debugger | | Golang | delve |

The required setup to debug a Go app running inside a Docker container is non-trivial. In this post I will walk through the configuration to achieve this using VSCode and the Delve debugger.

It’s awesome to use the powerful DELVE debugger for GO inside Visual Studio Code when you build a GO Operator. 🙂

dap.adapters.go = function(callback, _) local stdout = vim.loop.new_pipe(false) local handle local pid_or_err local port = 38697 local opts = { stdio = { nil, stdout }, args = { "dap", "-l", "127.0.0.1:" .. port }, detached = true, } handle, pid_or_err = vim.loop.spawn("dlv", opts, function(code) stdout:close() handle:close() if code ~= 0 then print("dlv exited with code", code) end end) assert(handle, "Error running dlv: " .. tostring(pid_or_err)) stdout:read_start(function(err, chunk) assert(not err, err) if chunk then vim.schedule(function() require("dap.repl").append(chunk) end) end end) -- Wait for delve to start vim.defer_fn(function() callback { type = "server", host = "127.0.0.1", port = port } end, 100) end -- https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_dap.md dap.configurations.go = { { type = "go", name = "Debug", request = "launch", program = "${file}", }, { type = "go", name = "Debug test", -- configuration for debugging test files request = "launch", mode = "test", program = "${file}", }, -- works with go.mod packages and sub packages { type = "go", name = "Debug test (go.mod)", request = "launch", mode = "test", program = "./${relativeFileDirname}", }, } ```

I’ve found Delve (debugging tool) quite useful for Emacs. It uses the plugin from VS Code, so you might be halfway there already? Figure out what you need to configure in Emacs for debugging here.

For Go, Delve is pretty popular.