Some nice features

[Steven Suson]

I've been wondering the same thing for some time now. Anyone who is new
to C++ development on Linux, always raises this objection. Personally,
I've found two workarounds:
1) Step INTO the constructor
2) Make the meat of the constructor a _ctor method, and have the real
constructor call this (where a break point can be set).
Is there any progress being made on this front that someone knows about?

Steven Suson

Harald Nikolisin wrote:

>and above all since many years the GCC under Linux is not able to stop
>at breakpoints in a constructor!
>I read some blabla at GCC-lists, why it's a problem, for me sounds very
>lazy (no I'm not able to fix it by myself, it's a pity)
>GCC on Mac OS X is able to stop and Visual C++ under Windows also.
>
>Maybe ICC is better, but then you have the complete overhead with
>specific libraries which are not available at the target computers and
>so on.
>
>That's really a very negative impression when Visual folks see this
>behaviour on a KDevelop environment, although KDevelop is not
>responsible for it.
>
>  harald
>
>leonp at plris.com schrieb:
>
>  
>
>>Hello, all.
>>
>>I think this will be nice to have the following options/features in debugger:
>>
>>1. Mouse pointer hoovering over a variable causes its value to appear in some 
>>callout/balloon (as in ddd);
>>2. An option to view memory starting from the variable address, while the 
>>variable may be pointed out in source or in watch windows (by right click 
>>menu).
>>3. Memory window can remember its last call parameters.
>>
>>Any comments?
>>Thanks.
>> 
>>
>>    
>>
>
>
>  
>

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«