I have tried all the same stuff, folowing the instructions, I have a test
program compiled with -g i load it into pose i start gdb with the file
then type target pilot localhost:2000 and i get this.
(gdb) target pilot localhost:2000
Remote debugging under PalmOS using localhost:2000
Waiting... (Press Ctrl-C to connect to halted machine)
then i start my program under POSE nothing, then i hit control-c and get
Sending query. (Press Ctrl-C again to give up)
0x10c8296c in ?? ()
Im not sure what im doing wrong? How come gdb doesnt break when i start my
program i knwo i comiled it with the -g option and i even recompiled it
jsut to make sure. Thanks for any help.
Scott Knight
On Wed, 1 Dec 1999, Vereecke Jan wrote:
> Thanks for this information. I used it as a start for my debugging under
> Win95. I have however still a problem with the last step: 'start debugging'.
> My problem is that I don't understand how I should get the debugger know the
> appropriate sources and symbols. Let me give an example. I have a program
> consisting of test.c, test.h and test.rcp.
>
> I build the program with the following steps (working under Win95):
>
> pilrc test.rcp
> m68k-palmos-coff-gcc -O1 -c -mdebug-labels test.c -o test.o
> m68k-palmos-coff-gcc -O1 -g test.o -o test
> m68k-palmos-coff-obj-res test
> build-prc test.prc "Test" "TST1" *.grc *.bin
>
> Then I try the steps you advise (with a ROM from my PalmV):
> > - Start Poser.
> > - Load your app into Poser.
> > - Start gdb.
> I use C:\Program Files\Palm Development\bin\m68k-palmos-coff-gdb.exe test
> > - Type "target pilot localhost:2000" to gdb.
> > - Start your app on Pose.
> > - Wait for gdb to see the initial breakpoint and prompt you.
>
> The result here is
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x26df0 in DbgSrcBreak ()
> (gdb)
>
> when I next try to set a breakpoint:
> (gdb) 'break EventLoop'
> I get the result
> Function "EventLoop" not defined
> (gdb)
>
> when I next try to set
> (gdb) 'break PilotMain'
> I get the result
> Breakpoint 1 at 0x27110
> (gdb)
>
> So it looks like PilotMain somehow got into the symbol table, but EventLoop
> and all other functions I defined not. So what should I do to be able to
> debug symbolically (using line numbers, function and variable names) ?
>
> As an extra tip, when I try the command 'list', I get 'gcrt0.c: No such file
> or directory'
>
> All tips and experience are welcome.
>
>
