If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I was saddened not to be able to comment on the original blog post - I've used gdb for years for many tasks, and it's perfectly suited to debugging in all the scenarios I ran into. If you want something more GUI oriented, I would recommend

There are some good gdb front-ends out there. Does this developer not know about them? I too don't use gdb directly, since CLI is not good enough for debugging. I need to always have the information I need on the screen without having to scroll through a text terminal. And a front-end allows for that.

It would seem that this developer doesn't know enough about Linux to actually be porting games to it.

After all the bullsh*t i saw in the comments i had to reply

For all of you saying that those developers don't know about Linux enough to develop for it the only thing i have to say is:
- knowing about Linux is different of knowing about the many GUI for GDB (which happens to be a GNU Project not a Linux foundation one)
- GDB (CLI version and the basic GUI versions that come in IDEs like codeblocks) _is_ limited when compared to VS10+ or the Intel debugger
- the fact that you have to know that you have to disable a driver when installing other is not something a Linux user shouldn't be proud of

Instead of saying things that can make those guys abandon ship, support them by giving them tips on how to improve their productivity

I'm pretty sure code::blocks use a deprecated annotation mechanism in gdb. He should really update to a modern IDE or use a standalone gdb frontend. Eclipse, Kdevelop, qtcreator or emacs is using the better modern mecanism.

For all of you saying that those developers don't know about Linux enough to develop for it the only thing i have to say is:
- knowing about Linux is different of knowing about the many GUI for GDB (which happens to be a GNU Project not a Linux foundation one)
- GDB (CLI version and the basic GUI versions that come in IDEs like codeblocks) _is_ limited when compared to VS10+ or the Intel debugger
- the fact that you have to know that you have to disable a driver when installing other is not something a Linux user shouldn't be proud of

Instead of saying things that can make those guys abandon ship, support them by giving them tips on how to improve their productivity

So what are the limitations of the GDB (not the CB gui for it) compared to CDB and IDB?