[cdt-debug-dev] CDT 1.2.0.50 success story for arm JTAG eCos development

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

I've now upgraded to CDT 1.2.0.50 and it has resolved the
issues with attach source and CygWin paths and a handfull
of other quirks (terminate now terminates the arm-elf-gdb.exe
process) :-)


- I use the "CygWin GDB debugger"
- The bdigdbinit attached  (for a BDI2000 JTAG debugger
and EB40a evaluation board)

The only thing that stops CDT from working out of the box
is that I need to modify plugin.xml(patch attached).



Øyvind

Attachment: bdigdbinit
Description: Binary data

Index: plugin.xml
===================================================================
RCS file: /home/tools/org.eclipse.cdt.debug.mi.core/plugin.xml,v
retrieving revision 1.16
diff -u -r1.16 plugin.xml
--- plugin.xml	23 Apr 2003 15:02:59 -0000	1.16
+++ plugin.xml	19 Sep 2003 09:18:13 -0000
@@ -25,7 +25,7 @@
             platform="native"
             name="%GDBDebugger.name"
             modes="run,core,attach"
-            cpu="native"
+            cpu="native,arm"
             class="org.eclipse.cdt.debug.mi.core.GDBDebugger"
             id="org.eclipse.cdt.debug.mi.core.CDebugger">
       </debugger>
@@ -33,7 +33,7 @@
             platform="win32"
             name="%CygwinGDBDebugger.name"
             modes="run,core,attach"
-            cpu="native"
+            cpu="native,arm"
             class="org.eclipse.cdt.debug.mi.core.CygwinGDBDebugger"
             id="org.eclipse.cdt.debug.mi.core.CygwinCDebugger">
       </debugger>
@@ -41,7 +41,7 @@
             platform="native"
             name="%GDBServer.name"
             modes="run"
-            cpu="native"
+            cpu="native,arm"
             class="org.eclipse.cdt.debug.mi.core.GDBServerDebugger"
             id="org.eclipse.cdt.debug.mi.core.GDBServerCDebugger">
       </debugger>