4 ms·
When I think debugger, I think gdb, which is fine to a point. But after a while, its interactivity becomes a liability. I don't want to have to set the same b
by drblast 16y ago
When I think debugger, I think gdb, which is fine to a point. But after a while, its interactivity becomes a liability. I don't want to have to set the same breakpoints and watches after a recompile, every time.
The integrated debuggers in IDE's are much better, particularly the Java ones. The C/C++ ones have the problem that they will work fine on code compiled with debug symbols, but on release code they're awful.
And when it comes down to it, the really hard to fix problems are the ones that only show up in the optimized release code.
- vilya 16y agoYou can rebuild your program while you're running gdb on it. Next time you restart the program you're debugging, it will pick up the rebuilt version and all your breakpoints and watches will still be intact. There's even a built-in gdb command for running make, for precisely this reason.