This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

"Unrecognized demangle component" error



  I've got this big executable (that uses the wxWindows library, a huge C++
cross-platform gui api), built with gcc version

(GCC) 3.3.3 (cygwin special)

and binutils version

GNU assembler 2.15.91 20040725

(they all report the same timestamp).  When I try debugging it with gdb, I
found that all the line number info was badly messed up.  So I thought I'd
take a look at the debugging info with objdump and see what I could see, and
what I saw was this:

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

  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.  I'm not too familiar with the internal gdb
commands for trying to debug these problems, so I was wondering if anyone
had a few suggestions to try?  Here's an example of how wrong it goes:

dk@mace /artimi/firmware/build/debug-i686-pc-cygwin/macsim> gdb ./macsim.exe
GNU gdb 2003-09-20-cvs (cygwin-special)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) list main
29      } tBerPoint;
30
31      // This class should be specialised for concrete phy layers
32      class CphyLayer
33      {
34      public:
35          CphyLayer(){}
36          virtual ~CphyLayer(){}
37
38          // Frame detection
(gdb)


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]