Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] Embedded toolsets

On Wed, 2003-01-22 at 23:34, Chris Songer wrote:
> 
> >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.
> 
> Because the extension model at the moment is go in and make it do what you 
> want by changing or cloning org.eclipse.cdt classes rather than use 
> extension points, I've been all through this. Here's what you should try:

Thanks for all this. I'm starting to get a much better idea of how it
all holds together now.

For anyone who's interested the GNU PalmOS toolchain uses COFF rather
than ELF so the state of the ELF parser is not really relevant (I've
just left the CPU as native for now). Do we have a COFF parser at the
moment?

Anyhow I've fixed the crash in GDB (my own bad porting) and actually got
a debug session running though it didn't work very well. I assume that a
Palm implementation of
org.eclipse.cdt.debug.mi.internal.ui.CDebuggerPage is my next port of
call?


	Cheers

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

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


Back to the top