In my experience, the cgdb [1] wrapper makes gdb a viable option, by providing what I think is the sorely missing piece in vanilla gdb: a window continuously sh

In my experience, the cgdb [1] wrapper makes gdb a viable option, by providing what I think is the sorely missing piece in vanilla gdb: a window continuously showing the code context. It also uses vim-like bindings for going into "insert" mode ("i"), versus escaping out into code context navigation mode ("ESC"). I made a short 4 minute tutorial on how to use gdb/cgdb for debugging Golang, here: https://www.youtube.com/watch?v=OKLR6rrsBmI https://www.youtube.com/watch?v=OKLR6rrsBmI [1] https://cgdb.github.io/ https://cgdb.github.io/