Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: mrcompiler@mrcompiler.com
Cc: Jim Blandy <jimb@redhat.com>, gdb@sources.redhat.com
Subject: Re: Multi-Arch symbol read warning message
Date: Sat, 22 Feb 2003 16:20:00 -0000	[thread overview]
Message-ID: <20030222162051.GA21801@nevyn.them.org> (raw)
In-Reply-To: <20030222031649.26686.qmail@admin1.cvtt.net>

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


  reply	other threads:[~2003-02-22 16:20 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
2003-02-22 16:20     ` Daniel Jacobowitz [this message]
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=20030222162051.GA21801@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=mrcompiler@mrcompiler.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