| RE: [cdt-dev] Proof in the pudding |
|
I thought Alain always preferred doughnuts…
___________________________________________
Chris Recoskie Software Designer Texas Instruments, Toronto http://eclipse.org/cdt
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Brian Foote
Having the debugger “just work” was also one of the most genuinely surprising and gratifying experiences we had during the early Photran days. So yes, kudos to the debug dudes. We still owe you a beer. Now Doug does too.
--BF
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Hey gang,
As I mentioned in the *DT bug report, I am playing with extending the CDT to do Ada. I spent a half an hour this morning setting things up and I was shocked at how much I got going.
Here are a couple of screenshots of the Editor and Debugger working with Ada. I am using gnatmake in Standard Build as my builder and created a Make Target to pass in the name of the Ada unit I wanted to build and the –g option for debug symbols.
http://cdt.eclipse.org/ada/AdaEdit.png http://cdt.eclipse.org/ada/AdaDebug.png I created the content types for Ada’s ads and adb files and hooked up the CEditor to those content types. Obviously the CEditor doesn’t know about Ada keywords and there’s no CModel populated for Ada things. But I don’t see this being too much work, and is something we need to do to properly support things like gcc specific keywords.
The biggest surprise was that breakpoints and the debugger just worked. A lot of this has to do with the multi-lang capabilities of gdb but also with the fact that the CDT’s debugger hasn’t forced language on the debug session, at least from what I can tell. Great work debug team!
Cheers, Doug |
