[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Embedded toolsets
|
>
> Hi Folks
>
> I have been using eclipse to develop applications for PalmOS. Now that
> the debugger is starting to mature a bit I would like to wire up gdb for
> PalmOS to eclipse. For those unfamiliar with the PalmOS toolchain be
> assured it is very much like any other cross-development GNU toolchain
> for more traditional embedded devices.
>
> Toward this end I have already ported the PalmOS gdb patch up to 5.3 in
> order to have the MI interface - this changed the error eclipse provided
> so I knew I was making progress.
>
> Anyhow I still get an error specifically:
> "An exception occurred while launching: Failed Launching CDI Debugger:
> No symbol "auto" in current context."
>
It is probably trying to set auto-solib on or off
(gdb)
4-gdb-set auto-solib-add on
4^done off
depending on your settings in the debugger path. And I guess, it fails.
Not sure what the best policy ... removing of this option?
Ignoring the error and keep on going ?
> I have downloaded CDT from CVS and built it within eclipse and had a
> look at it in a debugger. At this stage I wondered if consulting this
> list for hints about where to start might get me moving faster.
>
> Therefore ...
>
> Can anyone tell me how I can see the log of traffic traveling between
> the GDB and eclipse?
>
> Any hints on which classes I really need to understand to make any
> progress?
To see the dialog between gdb and CDT/Debug create a file call options
# cat options
org.eclipse.cdt.debug.mi.core/debug=true
and start eclipse with the -debug argument.
eclipse -debug file:<whever>/options
>
> Do you guys know of anyone who has used eclipse for cross-development yet?
yes, QNX, but QNX provides its own launcher etc ...
