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

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

>1 minute eh =;-)
>
>Well given the constraints of the Eclipse IDE and its workspaces it is 
>nearly as easy assuming that you have myimage.elf in your workspace:
>
>- Select Debug...
>- Select C/C++ Local
>- Main tab: Select your project, myimage.elf as the binary

This doesn't work currently, but the fix is being worked on:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=50584


>- Debugger tab: Select gdb server, TCP, your IP, your Port
>{Tricky Part}
>- Create a file with:
>   monitor reset
>   set $pc=0x1030000
>  in it and set it as the command file
>- Debug

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:

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.

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

>I'm sure that if you made contributions to work around this no one is
>going to complain =;-)

I did rummage around the CDT code and tweak it on one occasion
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=39061), but I'm not planning
on doing anything more until the "Eclipse 3.0/debugger changes" has been merged 
in(see 50584 above).


-- 

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