From: mrcompiler@mrcompiler.com
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Multi-Arch symbol read warning message
Date: Sat, 22 Feb 2003 03:23:00 -0000 [thread overview]
Message-ID: <20030222031649.26686.qmail@admin1.cvtt.net> (raw)
In-Reply-To: <vt2vfzemfo7.fsf@zenia.red-bean.com>
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?
Jim,
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[1]);
(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
something).
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]
[rs6000:rs2]
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
-I/vob/TORNADO/target/h -Wp,-MD,.deps/TORNADO/target/src/wv/mumble.d
-fno-builtin -c /vob/TORNADO/target/src/wv/mumble.c -o
TORNADO/target/src/wv/mumble.o
Here's some other example of "problem" namestring values,
1: "(100,39)=##(100,38);:;2A.;;"
1: "(100,46)=##(100,45);:;2A.;;"
1: "(100,52)=##(100,51);:;2A.;;"
1: "(101,
1: "(101,12)=##(101,11);:;2A.;;"
1:
"(101,12)=#(101,6),(101,9),(101,9),(0,20);:__Q310radix_node4$_834$_84;2A.;;,
0,96;\\"
1:
"(101,19)=#(101,13),(101,16),(101,16),(0,20);:__Q310radix_node4$_834$_85;2A.
;
;,0,96;\\"
next prev parent reply other threads:[~2003-02-22 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 22:30 mrcompiler
2003-02-21 4:23 ` Jim Blandy
2003-02-22 3:23 ` mrcompiler [this message]
2003-02-22 16:20 ` Daniel Jacobowitz
2003-02-22 3:46 ` Andrew Cagney
2003-02-22 17:32 ` mrcompiler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030222031649.26686.qmail@admin1.cvtt.net \
--to=mrcompiler@mrcompiler.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox