I've given it a try before. I really just prefer the -tui switch on gdb if I want to work with multiple panes. It allows src/console/registers/asm panes. really quite useful.

http://sourceware.org/gdb/onlinedocs/gdb/TUI.html

If you start gdb without -tui, and press ^Xo, it will switch to tui mode. I don't know if they've "fixed" this in newer versions, but I've found it useful.

That key sequence is emacs for switch to other window. If you're an emacs user but use gdb in the console it's the kind of thing you'll discover by accident sooner or later.

I am also familiar with the --tui switch for GDB and I'm wondering how this project is different. What does this project provide that gdb's tui mode does not? Can anyone that has used this expand upon why one would use cgdb over gdb's --tui mode?

With --tui there's no syntax highlighting or vim shortcuts. That's enough for me to prefer cgdb over gdb --tui. Update: I see it has scrollable gdb history, great feature!

That's enough for me to want to give it a shot! Thank you!

I do the occasional C++ debugging, and use gud-gdb in Emacs for that. I'm comfortable with Emacs, but I'm still a beginner when it comes to gdb.

Would there be a good reason for me to switch to cgdb?

I don't think there is a reason. GUD is very powerful and integrates well within Emacs. cgdb rather seems to be designed for vi users who don't want a debug interface in their editor.

I agree with this, gud is at least as good as cgdb.

There is also pyclewn, a plugin for vim that lets you interface with gdb.

http://pyclewn.sourceforge.net/