So is wrong with the GDB debugger? I hate to see Steam/Valve working on there own, if there is some simple things they could fix in an open source debugger.
The good thing about open source is you can fix and change. What makes the GDB debugger so bad? I find it extreamly useful and nice. The only big annoyance I ever had with it was some argument between the Compler and Debugger peoples about how C++ constructors worked. Couldn't set break points. I figure they got that figured out by now, that was like 10 years ago.
So, why create a new debugger, what is wrong with GDB, just don't say "its crap" what could be fixed in it.
Please fix your article to avoid possible flame war:
He clearly states that he prefers GTK over their home made GUI, not Qt:Originally Posted by Michael Larabel
I greatly prefer the native look and feel GTK gives us, rather than using our own
"home made" GUI.
There's nothing wrong with GDB. He's just using a Micky-Mouse kindergarten my-first-debugger GUI front-end to it, and then complaining when it doesn't have the functionality he needs.
If he really needs a GUI front-end to GDB, he should try DDD (Data Display Debugger,) it's actually not bad and has some useful struct visualization features.
Call Michael - unprofessional editor,
call that guy - newbie wannabie Linux developer,
but you can't deny one thing:
everytime one posts wrong assumption,
and posts it loud,
a forest of better ideas/corrections rises
Imagine for a sec, if that developer and Michael would keep all these private?
As some wise say:
say stupid thing and look stupid only till someone corrects you, or
keep your mouth shut, imitate wisdom, but in reality - stay stupid forever.