Use Vim to visually step through source code with GNU Gdb.
GNU Gdb is a great tool to debug your code. Many programmers develop their code using the terminal editor Vim, yet have to leave their beloved (often finely tuned) editor in order to start debugging efforts, because terminal options to visually step through code are limited to the Gdb TUI or cgdb. Vimgdb solves this, by connecting Gdb to your editing session in Vim.
Note: The example demonstrates Vimgdb while using Tmux, which allows the fast creation and navigation of vertical and horizontal terminal splits. Using it allows Vim and Gdb to be opened side by side.
-
GNU Gdb with python support. Verify in Gdb with:
(gdb) python-interactive -
Vim with clientserver capability. Verify by looking for +clientserver with:
vim --version
Vimgdb can be run from the root of its source directory by running bin/vimgdb-server and bin/vimgdb, but requires installation to be run from anywhere:
> python setup.py install
Start Vim:
> vimgdb-server [vim parameters]
From a different terminal, start Gdb:
> vimgdb [path/to/debug/binary]
Vimgdb functions are called througth events and hooks, but can also directly be called (type 'help vimgdb' in gdb). In case Vim and Gdb are desynchronize, type:
(gdb) vimgdb reload
In case you want to jump to other files or functions in Vim, type:
(gdb) vimgdb goto <expression>
Where expression is decoded in the same way as GDB's builtin break or edit commands. For example:
(gdb) vimgdb goto main
(gdb) vimgdb goto main.cc:8
Using the vimgdb-server command, Vim is started as a server such that Gdb can connect to it. Gdb is started upon calling vimgdb. Information about the current execution state is passed from Gdb to Vim upon triggering a hook or event, e.g., hitting a breakpoint, stepping though code, moving up and down the call stack, etc. The corresponding file will be opened in Vim, breakpoints highlighted and the current line of execution indicated.