Yeah, gdb really really sucks. I was yet again reminded of this today when trying to debug some multithreaded qemu code.
I am using gdb sometimes and it is just fine. Especially with the Python scripting support now. I used the Eclipse CDT gdb wrapper once and that, I agree, really sucks.
Yes. A thousand times yes.
> I used the Eclipse CDT gdb wrapper once and that, I agree, really sucks.
Just curious, how long ago was that? My opinion of Eclipse kind of ebbs and flows. I've used the GDB support a bunch for remote debugging of embedded systems (including, surprisingly, the Linux kernel).
In fairness, my gripe was always more with the IDE than its debugger support. CDT has always felt like the red-headed stepchild in comparison to Java support. The extra intelligence is nice, but it makes it so that you have to jump through lots of hoops to get it to be even remotely usable with a large codebase (again, the Linux kernel). Even on smaller codebases it can consume a buttload of memory and still be quite slow. But the debugger interface always seemed to "just work" for me.
This probably isn't good advice, but I really like VIM/pyClewn as a GDB frontend. Otherwise, there's always Eclipse, and 8 billion other IDEs.