Re: [cdt-debug-dev] CDT & RCP

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

> - try to remove the requirement that a debug session requires a project.
>  Perhaps by implementing an EmptyProject class.

I see at least two problems:
1. Assuming the executable is not built with full paths, the user has to 
setup the source lookup path for each session.
2. There is no way to set a breakpoint before the session.

----- Original Message ----- 
From: "Øyvind Harboe" <oyvind.harboe@xxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Tuesday, November 15, 2005 4:16 PM
Subject: [cdt-debug-dev] CDT & RCP


After a bit of tinkering I figured out how to build a first version of a
standalone CDT using RCP.

27Mbyte download size as a first attempt(assumes Java already installed
on the machine) isn't bad at all.

Windows snapshot: http://www.zylin.com/gdbgui-20051115.zip

These are my next steps:

- try to remove some more unecessary components(e.g. Update, managed
 Make, CVS support, etc.).
- try to remove the requirement that a debug session requires a project.
 Perhaps by implementing an EmptyProject class.
- test w/ARM JTAG debugging
- post new binary snapshot for comments

stage #2(assuming that it doesn't get shot down :-):

- try to compile w/GCJ, thus removing dependency on Java
- alternatively include JRE in download(it only adds ca. 10Mbytes).

Although the GDB GUI will be fairly expensive in terms of download size,
it has the potential to be cheap in terms of the number of concepts that
the developer needs to learn to get going w/GDB debugging.

For more advanced users there is always Eclipse CDT.


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

_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev