[cdt-debug-dev] Re: cdt-debug-dev digest, Vol 1 #218 - 1 msg

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

> >All I want CDT to do, is to step out of the way and let me=20
> >talk to GDB. Nothing would make me happier than if I could:
> 
> Aha!  And right there, that is the principal problem.  What=20
> assumption is there that you are talking to GDB, or that you
> are working with anything that actually even has a command line.

??

CDT allows me to talk directly to GDB through the console.

> The idea of the CDI interface is that you can abstract the=20
> debugger operation such that it can be used for a large number
> of different debugger back-ends.

For me GDB is the only game in town, and thus it is a disadvantage to me
that CDT allows other debuggers to be plugged in, because it draws away
precious development resources from polishing the GDB support.

> What I would suggest then is that you experiement with a custom
> launcher which is GDB specific to come up with a workflow that
> suits your needs in terms of its generality.  As I mentioned,=20
> I don't think that you are going to run into anyone opposing
> that kind of contribution, but at the same time the people who
> are working on the CDT currently don't have this type of need
> in their product(s); it looks like you do.

I strongly believe that very little is needed to allow the developer to
use GDB for all the things that Insight/DDD can be used for. I don't
think creating a new plugin is the right thing to do here.

I've sumbitted a patch to remove one tripwire:

http://dev.eclipse.org/mhonarc/lists/cdt-patch/msg02298.html

> For the general team, I think that that
> work is a ways off, but if you are interested, contributions
> are always welcome =3D;-)

Since I believe that a couple of tweaks in the CDT GDB plugin will do
the trick, I'll submit a couple of patches and see what happens.

-- 

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