Re: [cdt-debug-dev] Embedded toolsets

[Daniel Thompson <daniel@xxxxxxxxxxxxxxxxxxxxx>]

On Tue, 2003-01-21 at 18:23, Alain Magloire wrote:
> The CDT/Debug plan is very agressive(see other posting) but one thing is lacking
> is the capability to provide (remote) targets.  The idea was to provide
> an extension point, where one could implement an ITargetProvider etc ..
> The notion of "target" is a little fuzzy because it has to be tied with
> the builder (cross-dev, building for a specific target), the debugger
> (debugging a remote target, via serial/IP (gdbserver or other proxies)) and
> other module within the CDT.
> 
> We are lacking time for this so I doubt the entire framework will be in
> place for the next release ... but if you want to have a spin at it
> I'll be happy to assist.

I'm somewhat interested in this. I'll need to learn a fair bit more
about the Eclipse (and CDT) architecture before making much progress
though. At present I am dabbling with a PalmOSGDBDebugger class (in the
same vain as the CygwinGDBDebugger class). From the Eclipse point of
view this is working but unfortunately Eclipse generates commands that
cause gdb to crash so I will have to fix gdb before I can progress much
I'm afraid.

I can clearly appreciate that PalmOSGDBDebugger is a bad long term since
without contributing to the GUI we cannot customize the target command
(hence it is hardcoded at the moment to connect only to a simulator).
I'm only starting here because I'm one of those programmers that likes
to evolve something that works rather than forge an unproven
architecture.

Short term I do have one question however. At the moment I have got
Eclipse to use PalmOSGDBDebugger simply by altering the class name for
the native debugger in plugin.xml.

     <debugger
            platform="native"
            name="%GDBDebugger.name"
            modes="run,core,attach"
            cpu="native"
            class="org.eclipse.cdt.debug.mi.core.PalmOSGDBDebugger"
            id="org.eclipse.cdt.debug.mi.core.CDebugger">
      </debugger>

I have tried adding other debugger entries (and I have kept
plugin.properties matching the name field) but I can not get the changes
I make to plugin.xml to be reflected in the debugger drop down in the
launchers debugger tab. Whatever I do the list remains stubbornly empty
- it does not even contain the GDB Debugger that the box has selected
let alone the Cygwin entry or my Palm one.

	Cheers

	Daniel
	--xx--
-- 
Daniel Thompson (Merlin) <daniel@xxxxxxxxxxxxxxxxxxxxx>

If at first you don't succeed then sky diving is probably not for you.