[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Which development tools do you use ?
From:       Guillaume Laurent <glaurent () telegraph-road ! org>
Date:       2001-10-18 8:00:23
[Download RAW message or body]

On Wednesday 17 October 2001 20:12, John Gluck wrote:
>
> As processor get more complex and languges develop more features, the debug
> tools naturally get more complex to be able to show the maximum info.

No, gdb hasn't evolved in years, UI wise. A debugging tool can get more 
complex internally (needing to parse more complex structures, etc...), but 
that doesn't mean it should be so externally. I should still be able to click 
on a variable to display its contents, or to easily select a class method 
where to put a breakpoint on.

> One thing is if you use a class as a data member, you can examine the data
> member class.
> Also, if you have a pointer to a parent class, you can examine the parent.
> You can also modify variables more easily.

OK, that's good to know.

> You haven't lived till you've debugged by [...]

Can we please cut the war stories here ? :-)

> If you want maximum debugging, you have to roll up your sleeves and dig.

I want efficient debugging, not "maximum debugging". Single-stepping in 
assembly or having access to the code at the binary level is generally 
useless when I'm dealing with a C++ application of several megabytes, except 
in some very rare cases. But in general that won't help me find why an STL 
iterator is invalid or why that widget won't draw properly, or knowing what 
are the contents of this hash table.

-- 
Guillaume
http://www.telegraph-road.org
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]