From: "Dave Korn" <dk@artimi.com>
To: <binutils@sources.redhat.com>, <gdb@sources.redhat.com>
Subject: "Unrecognized demangle component" error
Date: Fri, 22 Oct 2004 15:01:00 -0000 [thread overview]
Message-ID: <NUTMEGh05YFRcmVFOh100000198@NUTMEG.CAM.ARTIMI.COM> (raw)
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....
next reply other threads:[~2004-10-22 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 15:01 Dave Korn [this message]
2004-10-24 18:50 ` Ian Lance Taylor
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=NUTMEGh05YFRcmVFOh100000198@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=binutils@sources.redhat.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