From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16312 invoked by alias); 22 Feb 2003 16:20:59 -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 16294 invoked from network); 22 Feb 2003 16:20:59 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 22 Feb 2003 16:20:59 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18meHi-00064q-00; Sat, 22 Feb 2003 12:22:03 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18mcOR-0005gL-00; Sat, 22 Feb 2003 11:20:51 -0500 Date: Sat, 22 Feb 2003 16:20:00 -0000 From: Daniel Jacobowitz To: mrcompiler@mrcompiler.com Cc: Jim Blandy , gdb@sources.redhat.com Subject: Re: Multi-Arch symbol read warning message Message-ID: <20030222162051.GA21801@nevyn.them.org> Mail-Followup-To: mrcompiler@mrcompiler.com, Jim Blandy , gdb@sources.redhat.com References: <20030220222419.21758.qmail@admin1.cvtt.net> <20030222031649.26686.qmail@admin1.cvtt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030222031649.26686.qmail@admin1.cvtt.net> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00496.txt.bz2 On Fri, Feb 21, 2003 at 07:16:49PM -0800, mrcompiler@mrcompiler.com wrote: > 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. At an off-the-wall guess, the problem is that ARM tools use continuation characters in stabs and PowerPC tools don't. Are you sure a plain arm-vxworks debugger doesn't show the same thing? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer