Sorry for brining this back again,
but with the instructions given by "BPetersen" in his message to this thread
on
Oct. 31 (see below)
I still can not load the sym file into PalmOs 3.5 PalmDebugger from Palm
Computing, Inc. I get the following message in the debugger window:
----------------------------------------------------------------
Using symbol file: C:\WN16\my\ui\XXXX.code.1.sym
Error: SymFileAdd: Invalid symbol file: C:\WN16\my\ui\XXXX.code.1.sym. Bad
line
count
----------------------------------------------------------------
The version of m68k-palmos-gcc I use is "2.95.2-kgpd".
Could it be that something has changed since Oct 31?
Here is what I do in my Makefile:
----------------------------------------------------------------
EXEC = xxxx
EXEC2 = XXXX.code.1.sym
# compiler flags
CCFLAGS = -Wall -palmos3.5 -DDEBUG -g -O0
# compile requirements
$(EXEC).prc: $(EXEC) $(EXEC).def bin.stamp
$(BUILDPRC) $(EXEC).def $(EXEC) *.bin
$(EXEC): $(OBJS)
$(CC) -g $(OBJS) -o $(EXEC2)
cp $(EXEC2) $(EXEC)
-----------------------------------------------------------------
Here is a fragment from the "Palm OS Programming Development Tools Guide:
A symbol file contains the following items:
. the names of each of the source files that were linked together
to create the code resource
. the offset from the start of the code resource to the object
code for each source file
. the offset from the start of the code resource for each line in
the source file
. descriptions of the data structures used
. descriptions of the name, type, and location of each local
variable used in the source code's functions
. descriptions of the name, type, and location of each global
variable
--------------------------------------------------------------------
The file sym file that gets produced is just a regular executable
which looks nothing like described above.
Bellow is the original message to this thread.
Thanks,
Yuri
======================================================
Older versions of the PalmDebugger distributed by Handspring that have
source-level debugging capability are looking for a "sym" file (created as
Keith describes) with a specially-formatted name. The name looks like
"<Database name>.<resource type>.<resource id>.sym".
For example, if your app has a database name of "PocketFoo" and you are
loading the main symbols, you want to rename your linker output to
"PocketFoo.code.1.sym". This will load the symbols for the code.1 resource
for your app (the main code resource).
A makefile I just pulled out at random has the following link line:
$(CC) $(CFLAGS) $(appObjList) -o $(objDir)/$(progDBName).code.1.sym
The output file is then passed on to the post-linker with the "sym" name.
Obviously, this is a bit cumbersome. The newest version of PalmDebugger
that Handspring is distributing with their development kit finds the most
commonly named symbol files automatically, with or without a special name.
This development kit also supports new stuff for the Visor Prism, etc. You
can find it here:
<http://www.handspring.com/developers/developers_kit.jhtml>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
