Ben Combee <[EMAIL PROTECTED]> wrote: > > >>What happens is that gdbpanel sets the 'gdbS' feature. The gdb startup >>code (when linked with -g) looks for this feature. If it is present it >>will break at PilotMain, if not the app will run normally. >>POSE sets this feature automatically, so you do not need gdbpanel when >>debugging with POSE. When you want to debug on a real device you will also >>need gdbpanel. > > Ton, why doesn't GDB just use the RPC interface to call FtrSet to setup > thie 'gdbS' before it downloads the application to the > device/emulator? That would eliminate the need to have gdbpanel or any > POSE hacks. > As John Marshall already replied it would be better to not use the 'gdbS' feature at all and get all the information via RPC. Moreover there is currently no support to download a prc/pdb/file to the device/emulator in gdb. This has to be done outside gdb.
Maybe more urgent right now is to get gdb working correctly on the Tungsten-T. Gdb relies on the trace-trap for the step command. As you know PACE skips the first (68k) instruction when tracing starts. Also support for USB debugging is missing. So plenty of work for palm gdb enthusiasts .... Ton van Overbeek -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
