3 ms·

On Emacs, I'd recommend using M-x gdb, rather than running gdb through GUD (which is M-x gud-gdb). Emacs has a much tighter integration with gdb than with othe

On Emacs, I'd recommend using M-x gdb, rather than running gdb through GUD (which is M-x gud-gdb). Emacs has a much tighter integration with gdb than with other debuggers. The features and interface are documented here: https://www.gnu.org/software/emacs/manual/html_node/emacs/GDB-Graphical-Interface.html#GDB-Graphical-Interface https://www.gnu.org/software/emacs/manual/html_node/emacs/GD...

evmar 6y ago
After 10 years as a vim user, I switched to emacs in part for the gdb integration. (It turns out you can run emacs with vim keybindings and get the best of both worlds -- vi keybindings but a real programming language for scripting...)
- xyproto 6y ago
  You also get the sluggishness of Emacs, though. Slow startup and syntax coloring, compared to ViM and NeoViM.
  - AsyncAwait 6y ago
    Daemon mode is your friend.
  - donaldihunter 6y ago
    Worth trying Emacs 28. The speedup is impressive. https://news.ycombinator.com/item?id=24117853 https://news.ycombinator.com/item?id=24117853
  - segfaultbuserr 6y ago
    > Slow startup Simply run Emacs in server mode - it's an operating system, so don't shut it down too often ;-)
pksadiq 6y ago
And it's much better when used with gdb-many-windows and speedbar
convolvatron 6y ago
this has been a total mess for me (cue the xkcd about the spacebar and thermal throttling). using emacs in terminal mode its pretty frustrating to have the gdb interface bring up windows that you aren't allowed to delete...that and I can I really do more than 2 or 3. so whatever the intent was has been well and truly lost. this kind of modality is anti-emacs...at least why my hindbrain thinks of as emacs working on compiler-introduced introspection annotations and writing an elisp front end. we'll see.
MetaDark 6y ago
I prefer using dap-mode. It has a much nicer interface that's consistent across multiple debuggers. I use it for C, C++, Rust (Native Debug + gdb) and Python (debugpy).

evmar 6y ago

After 10 years as a vim user, I switched to emacs in part for the gdb integration. (It turns out you can run emacs with vim keybindings and get the best of both worlds -- vi keybindings but a real programming language for scripting...)

xyproto 6y ago
You also get the sluggishness of Emacs, though. Slow startup and syntax coloring, compared to ViM and NeoViM.
- AsyncAwait 6y ago
  Daemon mode is your friend.
- donaldihunter 6y ago
  Worth trying Emacs 28. The speedup is impressive. https://news.ycombinator.com/item?id=24117853 https://news.ycombinator.com/item?id=24117853
- segfaultbuserr 6y ago
  > Slow startup Simply run Emacs in server mode - it's an operating system, so don't shut it down too often ;-)

pksadiq 6y ago

And it's much better when used with gdb-many-windows and speedbar

convolvatron 6y ago

this has been a total mess for me (cue the xkcd about the spacebar and thermal throttling). using emacs in terminal mode its pretty frustrating to have the gdb interface bring up windows that you aren't allowed to delete...that and I can I really do more than 2 or 3. so whatever the intent was has been well and truly lost. this kind of modality is anti-emacs...at least why my hindbrain thinks of as emacs working on compiler-introduced introspection annotations and writing an elisp front end. we'll see.

MetaDark 6y ago

I prefer using dap-mode. It has a much nicer interface that's consistent across multiple debuggers. I use it for C, C++, Rust (Native Debug + gdb) and Python (debugpy).