This is the mail archive of the
mailing list for the GDB project.
Re: Multi-Arch symbol read warning message
Jim Blandy writes:
If you set a breakpoint
on the appropriate 'complaint' call in dbxread.c:read_dbx_symtab and
'print namestring' when you get there, what does it say?
Thanks for the prompt response, the namestring value is below.
Breakpoint 3, read_dbx_symtab (objfile=0x2b3c38) at dbxread.c:2024
2024 complain (&unknown_symchar_complaint, p);
(top-gdb) print namestring
$1 = 0xbd089f "(10,7)=##(10,6);:;2A.;;"
It complains about the ';' symbol, I believe its the one in front of 2A.
Its kind of interesting that this only occurs when I specify the arm-vxworks
target, if I build a powerpc-vxworks target it doesn't happen.
It turns out that if I set the stop-whining value higher there are a number
of other messages (several thousand, most of which seem to dups with
different memory locations, possible the result of multiple library links or
I picked some at random and included an example of our build flags (we're
using gcc from Wind River). I don't see any problems from this, but that may
be because we use this version of GDB only for our core files.
It may also be significant that the host is Solaris.
Here's the supported architecture info:
(gdb) info architectures
Supported architectures are:
[arm] [armv2] [armv2a] [armv3] [armv3m] [armv4] [armv4t] [armv5] [armv5t]
[armv5te] [xscale] [powerpc:common] [rs6000:6000] [rs6000:rs1] [rs6000:rsc]
Here's an example of our build flags:
/vob/TORNADO/host/sun4-solaris2/bin/ccppc -pipe -ansi -I. -DCPU= PPCEC603
-mcpu=PPCEC603 -mstrict-align -msoft-float -DVXWORKS -D__vxworks__=1
-fno-builtin -nostdinc -nostdlib -fvolatile -fno-defer-pop -g -O2
-Wpointer-arit h -I/vob/ip/include -I/vob/infra/include
-fno-builtin -c /vob/TORNADO/target/src/wv/mumble.c -o
Here's some other example of "problem" namestring values,