RE: [cdt-debug-dev] Another graphics interface to GDB - DDD

[Thomas Fletcher <ThomasF@xxxxxxx>]

>-----Original Message-----
>From: Øyvind Harboe [mailto:oyvind.harboe@xxxxxxxxx]
>Sent: May 7, 2004 7:57 AM
>To: cdt-debug-dev@xxxxxxxxxxx
>Subject: [cdt-debug-dev] Another graphics interface to GDB - DDD

[Comments about binary selection snipped]

>
>My point is that CDT does not make things any easier by adding 
>all these debug menus. I don't want it to attempt to control the 
>launching of the application.
>
>Especially since I frequently make slight vartions on the 
>procedures above when connecting to the target, e.g. connecting 
>to a running target is somewhat different from rebooting the device. 
>
>All I want CDT to do, is to step out of the way and let me 
>talk to GDB. Nothing would make me happier than if I could:

Aha!  And right there, that is the principal problem.  What 
assumption is there that you are talking to GDB, or that you
are working with anything that actually even has a command line.
The idea of the CDI interface is that you can abstract the 
debugger operation such that it can be used for a large number
of different debugger back-ends.

>1. Enter the command line to launch the arm-elf-gdb. I could 
>forgive CDT for remembering the
>last command line, but I don't want any more help. :-) There 
>is of course the complication
>that GDB is often a CygWin executable, and hence the launching 
>of the GDB app needs to be
>flexible enough to allow for that. CDT should not assume that 
>the windows PATH variable is
>set to include CygWin executables. Having CygWin in the 
>Windows path is a source of missery.
>2. Once launched, CDT would let me enter GDB console commands. 
>CDT should not make any
>assumptions about whether GDB is currently attached to a debug 
>target, whether that target is 
>running or not, etc.

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

>Ideally, I'd like to be able to launch the CDT debugger from 
>the CygWin command line as well.
>
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=39640
>

Yes, it would be very interesting.  One approach to try as a 
starting point is to make an application launcher for it (ie
-application cdt-debug).  I know that there has been discussion
with regards to this and that the coupling is not so tight as
to make it impossible to even consider the debugger as an RCP
type of application.  For the general team, I think that that
work is a ways off, but if you are interested, contributions
are always welcome =;-)

Thanks,
 Thomas