[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To debug Palm OS applications, GDB needs to load symbolic information from the bfd executable corresponding to your application, and to be connected to the Palm OS device where the application is running. You generally specify the bfd executable on the command line (for example, to debug an application `myapp.prc')
$ m68k-palmos-gdb myapp |
and connect using the `target' command.
target palmos port
target pilot port
Using pilot
is equivalent to palmos
, and is provided for
compatibility with earlier releases. If port is omitted, GDB will
attempt to connect to `localhost:2000' by default.
(The prc-tools 2.0 release only supported the pilot
keyword, and
port was not optional.)
After you have connected to the device, you should enable the debugger stub (see section 5.1 Building an application with debugging enabled), which is done automatically if you are connecting to Poser, and start your application, which you've compiled and linked with `-g'.
When your application starts up, GDB receives data from the debugger stub telling it how to correlate the bfd executable's debugging information with where in memory the application has been loaded. Because of this, you need to ensure that the debugging information has been loaded before the breakpoint is received--hence typically the bfd file of debugging information is specified on the GDB command line.
The debugger stub also causes execution to stop as if at a breakpoint at
the start of PilotMain
, giving you a chance to interact with the
debugger before your program runs but after you're connected to it.
However, PilotMain
can be entered multiple times--for example,
if your application is sublaunched with another launch code or if you
(or a gremlin) switch to another application and back again--and you
may not want to break into the debugger every time. You can control
whether the debugger stops at this implicit breakpoint by changing the
way GDB handles the SIGSTOP
signal (see section `Signals' in Debugging with GDB).
There are some other features and limitations:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |