RE: "Unrecognized demangle component" error

["Dave Korn" <dk@artimi.com>]

> -----Original Message-----
> From: binutils-owner On Behalf Of Ian Lance Taylor
> Sent: 22 October 2004 20:53

> "Dave Korn" 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).

  OK, I quickly plumbed in those changes (using 2.15 release sources), and see
that they're all without exception references to type #34 which I make out to be
DEMANGLE_COMPONENT_FUNCTION_TYPE.  Ummm.  I would imagine that's a slightly
surprising result, perhaps?

> 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.

  Thanks Ian, I'll look into that one a bit further.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....