RE: [cdt-debug-dev] Re: How to set breakpoint in libraries

[Thomas Fletcher <ThomasF@xxxxxxx>]

>-----Original Message-----
>From: cdt-debug-dev-admin@xxxxxxxxxxx 
>[mailto:cdt-debug-dev-admin@xxxxxxxxxxx] On Behalf Of Øyvind Harboe
>Sent: October 25, 2004 12:27 PM
>To: cdt-debug-dev@xxxxxxxxxxx
>Subject: [cdt-debug-dev] Re: How to set breakpoint in libraries
>
>> > Alternative:
>> > 
>> > How about adding a "set breakpoint on current line" from the 
>> > right-mouse-click menu?=20
>> > 
>> 
>> As you pointed you can use the GDB console, (for other alternatives 
>> see the previous email).  But it does not provide 
>persistency and other Eclipse/UI features.
>
>Would it be possible to leave the IMarker/IResource/proxy 
>stuff for another day, and just add the "right click->add 
>breakpoint to current line" menu item?
>
>It would then translate into a GDB command

And it won't work for debuggers that aren't GDB!!!!

Why would you insist on implementing something that is wrong 
and poorly designed that we then have to live with when doing 
it right is only slightly more work?  If you really want to
do this, then you can create a custom plugin with a custom action
that _knows_ you are using GDB to debug and can send a direct
GDBCommand via MI.

>break foo.c:1234
>
>The feature wouldn't be complete, but it would be a big step 
>forward for those that use CDT for production. Also, this menu 
>item should be there even when the feature set is fleshed out more.

I agree that the feature is usefull (header files come to mind), but 
I don't want to see time spent on implementing something that is 
non-generic and hard-coded to GDB when it is possible to do it "right"
with a little more thought and a little more time.

-1

Thomas