From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25454 invoked by alias); 22 Feb 2003 03:23:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 25439 invoked from network); 22 Feb 2003 03:23:14 -0000 Received: from unknown (HELO admin1.cvtt.net) (209.133.53.91) by 172.16.49.205 with SMTP; 22 Feb 2003 03:23:14 -0000 Received: (qmail 26687 invoked by uid 89); 22 Feb 2003 03:16:49 -0000 Message-ID: <20030222031649.26686.qmail@admin1.cvtt.net> References: <20030220222419.21758.qmail@admin1.cvtt.net> In-Reply-To: From: mrcompiler@mrcompiler.com To: Jim Blandy Cc: gdb@sources.redhat.com Subject: Re: Multi-Arch symbol read warning message Date: Sat, 22 Feb 2003 03:23:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00493.txt.bz2 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;\\"