PalmDebugger.exe Source Window

[John Marshall]

FPD-HAWAII <FPD-H...@email.msn.com> wrote:
> I can not find a SYM file anywhere! I read that the LINKER has an option to
> write out this file... But I can not find it.

I'm told that the file PalmDebugger refers to as a "symbol file" is merely
the executable produced by the linker, which you give to obj-res/build-prc
(and you got by compiling with -g of course). This seems somewhat confusing
to me, but I suppose it's not much more confusing than referring to a file
that isn't executable as an executable :-).

> Error: SymFileAdd: Can't open E:\tutorial\Text to Hex.code.1.sym

To achieve maximum confusion, PalmDebugger has its own convention for what
it expects that file to be called, and it's different from what everyone
else who's ever used GCC calls it. When you run an app on your device,
PalmDebugger looks for a file named

<app's database header name>.code.1.sym

So either hack your Makefile to have the link command output this strange
name, or copy tex2hex to "Text to Hex.code.1.sym", possibly at the same
time as you run build-prc.

But, like Peter, I'd probably just use m68k-palmos-gdb. :-)

John

[FPD-HAWAII]

Help! I can not seem to get the Source window in the Debugger to work...
I get two info msgs in the Debugger and I guess I just do not understand
what I have to do...

I'm on a WIN98SE with the GCC compilier 3.5SDK

One msg is...

Error: SymFileAdd: Can't open E:\tutorial\Text to Hex.code.1.sym

I can not find a SYM file anywhere! I read that the LINKER has an option to

write out this file... But I can not find it.

I believe the second msg may be solved if the SYM problem is fixed.

In the SOURCE window I get this msg...

(Not stopped in source...)

What to do...

ALOHA

[Peter Burka]

As far as I know, PRC-Tools cannot output the symbol files required by the
Palm debugger. Only CodeWarrior can do that. You should be using gdb
instead (either m68k-palmos-coff-gdb for PRC-Tools 0.50 or m68k-palmos-gdb
for PRC-Tools 2.0).

/peter

[Gabo]

john_w_...@palm.com (John Marshall) wrote in
<q5orcqvt$GA....@www.massena.com>:

>FPD-HAWAII <FPD-H...@email.msn.com> wrote:
>> I can not find a SYM file anywhere! I read that the LINKER has an
>> option to write out this file... But I can not find it.
>

>I'm told that the file PalmDebugger refers to as a "symbol file" is
>merely the executable produced by the linker, which you give to
>obj-res/build-prc (and you got by compiling with -g of course). This
>seems somewhat confusing to me, but I suppose it's not much more
>confusing than referring to a file that isn't executable as an
>executable :-).
>

>> Error: SymFileAdd: Can't open E:\tutorial\Text to Hex.code.1.sym
>

>To achieve maximum confusion, PalmDebugger has its own convention for
>what it expects that file to be called, and it's different from what
>everyone else who's ever used GCC calls it. When you run an app on your
>device, PalmDebugger looks for a file named
>
> <app's database header name>.code.1.sym
>
>So either hack your Makefile to have the link command output this
>strange name, or copy tex2hex to "Text to Hex.code.1.sym", possibly at
>the same time as you run build-prc.
>
>But, like Peter, I'd probably just use m68k-palmos-gdb. :-)
>
> John

I try to copy the file ( in my case cookbook ) to the specific format but
the palm debugger still give me:
"Error: SymFileAdd: Invalid symbol file:
C:\desarrollo\cookbook\cookbook.code.1.sym. Bad line count"

I compiled with -g option and copy the output file from m68k-palmos-gcc (
the one without extention ).

any ideas?
Gabo