2 ms·
I used to get by primarily with print statements and occasional use of gdb either on the command-line or with the Emacs gdb mode. Back when I used Emacs and vi
by rleigh 5y ago
I used to get by primarily with print statements and occasional use of gdb either on the command-line or with the Emacs gdb mode. Back when I used Emacs and vim and I was something of a Linux zealot I never really considered anything else as being worthwhile.
However, over the last few years I've switched mostly to CLion, which has excellent support for gdb and gdbserver, so you can use it to debug local, remote and embedded applications directly on the target with a debug probe. It can't be understated just how much of a timesaver a graphical debugger is compared to controlling things through the CLI. Stepping in/out/over, setting breakpoints and watchpoints, viewing the call stack and individual frames, and jumping back and forth from source code to disassembly. You can do all this from the CLI, of course, but it's much less efficient.
As much as I despise Eclipse, even it manages to have excellent gdb and gdbserver support which is also vastly better than the CLI for debugging.