nvim-gdb VS gdb-dashboard

It's not ideal to me yet. I've had some problems with DAP. The DAP servers I've checked were a bit unstable and slow. For now I'm using gdb with nvim-gdb https://github.com/sakhnik/nvim-gdb

Very reliable and as fast as gdb is. But with all the problems just using gdb has.

Maybe https://github.com/sakhnik/nvim-gdb (bashdb uses gdb like commands) I've mostly used llvm debugger and node debugger so I am not too familiar with gdb.

nvim-gdb: GDB wrapper, simple and easy to hack.

Recently I am using nvim-gdb, which is inspired by neovim-gdb.vim script. I am wondering whether it is possible to have the same visual interface in terms of current line running as well as the breakpoint mark similar to the above two project but not connect to the debug?

There's the plugin that evolved from the original neovim debugger: sakhnik/nvim-gdb. Well tested and maintained. Spoiler: personal affiliation.

sakhnik/nvim-gdb This one also looks like a nice debugger plugin; also neovim only.

https://www.dannyadam.com/blog/2019/05/debugging-in-vim/ describes it well. https://github.com/sakhnik/nvim-gdb is nicer, but requires neovim.

To debug, termdebug is built in to vim and supports a front end to gdb. In combination with gdb-dashboard this gives a reasonably good debugging experience

https://github.com/cyrus-and/gdb-dashboard, https://github.com/cyrus-and/gdb-dashboard/wiki

You can use the Python API to GDB to get really fancy TUIs like this: https://github.com/cyrus-and/gdb-dashboard

Try GDB Dashboard, it makes gdb much easier to use:

https://github.com/cyrus-and/gdb-dashboard

There's also Voltron which works with both gdb and lldb (amongst others):

https://github.com/snare/voltron

I can't believe no one has mentioned `gdb-dashboard` [1] yet! I use it extensively. [2]

Beyond that, I have recently learned how to write custom pretty printers for GDB. This saves a lot of screen space. I should probably update [2] soon with those new techniques.

GDB is powerful, useful, and after getting my start in IDE debuggers, including Visual Studio, I struggle whenever I have to go back.

[1]: https://github.com/cyrus-and/gdb-dashboard

[2]: https://gavinhoward.com/2020/12/my-development-environment-a...

Debugging: Learn gdb. You can use it for assembly. You can use it for C on a MCU. You can use it for Go on a Linux system. It’s ubiquitous, versatile, and worth understanding. You can pretty-print the output with something like this to help you out at first. There are 2 things you need, however: on chip debugger and a debug probe (though you don’t need an expensive one). Effectively, you talk to GDB, GDB talks to the server exposed by OCD, OCD knows the debug probe protocol, and the debug probe can use the MCU debug peripheral via SWD or JTAG to get those details.

I use gdb because I'm usually in the terminal. I don't think terminal it's any faster though. This is a nice addition to boring old terminal gdb.