public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@wasabisystems.com>
To: "Dave Korn" <dk@artimi.com>
Cc: <binutils@sources.redhat.com>, <gdb@sources.redhat.com>
Subject: Re: "Unrecognized demangle component" error
Date: Sun, 24 Oct 2004 18:50:00 -0000	[thread overview]
Message-ID: <m3y8hyo7gx.fsf@gossamer.airs.com> (raw)
In-Reply-To: <NUTMEGh05YFRcmVFOh100000198@NUTMEG.CAM.ARTIMI.COM>

"Dave Korn" <dk@artimi.com> writes:

> --------------------<snip!>--------------------
> dk@mace /test> objdump -g macsim.exe
> 
> macsim.exe:     file format pei-i386
> 
> Unrecognized demangle component
> --------------------<snip!>--------------------
> 
>   Wow.  I've never before come across an error message that brings up so few
> hits at google.  That's probably because ILT only added it in January:
> 
> http://sources.redhat.com/ml/binutils/2004-01/msg00192.html
> 
> and I see from the following FIXME that it's not a big surprise that it
> sometimes fails:
> 
> +      /* FIXME: These are demangle component types which we probably
> +	 need to handle one way or another.  */

I wonder which component it was.  I should have had the error message
print it out the number.  It would probably also be friendlier to
print a warning and then return debug_make_void_type (dhandle).

>   Anyway, I don't know a lot about the interactions round here, but I was
> wondering if this problem could have had a knockon effect on gdb making it
> lose track of the line tables.

That is unlikely.  The demangled name is used to determine the
argument types and the return type of static methods.  It is not used
for anything involving line numbers.

I don't know what is causing the line number trouble.

Ian

  reply	other threads:[~2004-10-22 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 15:01 Dave Korn
2004-10-24 18:50 ` Ian Lance Taylor [this message]
2004-10-25 23:11   ` Dave Korn
2004-10-26  9:32     ` Ian Lance Taylor

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=m3y8hyo7gx.fsf@gossamer.airs.com \
    --to=ian@wasabisystems.com \
    --cc=binutils@sources.redhat.com \
    --cc=dk@artimi.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).