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

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

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

Before I get up on my soapbox:

If I didn't love Eclipse and CDT, I wouldn't bother trying to make it
work better for embedded development.

Further I see the necessity and usefulness of the plug-in system, and I
wouldn't have done it otherwise.

I'll get on my soapbox now: 

I believe GDB supports more architectures than all other debuggers
combined. I do not believe GDB is the most popular debugger.

If Eclipse CDT didn't come with a great GDB userinterface, I wouldn't
have been interested in Eclipse CDT debugging GUI at all. 

For the likes of me, it is the only debugger. To me it is a dis-feature
of Eclipse CDT that it supports other debuggers as it makes it harder to
implement sorely needed features, like "add breakpoint to current line".

The entire plug-in system has the, potentially, nasty side effect that
"plugins are left as an exercise to the reader". I have found nothing 
that is missing in Eclipse CDT w.r.t. embedded development that are not
either a) not done yet or b) simply a bug. No need for a new
embedded/GDB plugin.


> Why would you insist on implementing something that is wrong=20
> and poorly designed that we then have to live with when doing=20
> it right is only slightly more work?

I don't know enough about how to do this yet, but this is of course
preferable.

Ref. I am trying to fix my other patches to be more palatable.

>   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.

See above.

--

Øyvind Harboe
http://www.zylin.com