RE: [cdt-debug-dev] Re: Using CDT as avr-gdb frontent for AVR tar get pl

[Thomas Fletcher <ThomasF@xxxxxxx>]

>-----Original Message-----
>From: Alain Magloire [mailto:alain@xxxxxxx]
>
>> http://dev.eclipse.org/mhonarc/lists/cdt-patch/msg02298.html
>> 
>
>This is still subject to heavy debate on this side of the pound.
>About the "right" way to handle all of those targets cleanly
>whithout bloating the CDT.  The first approach, provide your
>launch and entry point seems to be to much for the casual
>users "who just want to run gdb on there XXX cpu".

I think that the solution is to use the current extension point to 
create a totally user customizable version of the debugger.  You can
use the current extension point to do that kind of generalization.
As a results you end up with 

Generic Extension Point Definition(s): 
 ISV/OEM's who want to fully control their implementation plug in
here and may or may not use the gdb world.

Then using the Generic Extension Point Definition(s) you can
have a "User Driven GDB" which can provide the appropriate 
controls to allow the user to
 1- Launch and arbitrary gdb they want
 2- Provide the ability to run some arbitrary commands before
    the session really gets going.

The problem is that right now there is no simple mechanism which 
allows the caller of the gdb process creation to intervene once
the gdb has been started, but before it has done anything meaningful.

Then of course you would have to build up the API around that.

Thomas