This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/7078] [3.3/3.4 Regression] stabs are not generated correctly with c++ namespaces are used
- From: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Jan 2004 21:58:41 -0000
- Subject: [Bug debug/7078] [3.3/3.4 Regression] stabs are not generated correctly with c++ namespaces are used
- References: <20020619070603.7078.salman.khilji@cae.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ian at airs dot com 2004-01-12 21:58 -------
This bug states that objdump -g can't handle gcc 3.1 stabs debugging
information. While part of the problem lies with the way gcc changed the
handling of qualified names in stabs debugging output, another part of the
problem lies with objdump. In order to parse stabs debugging information,
objdump needs to be able to demangle names. This is because g++ uses mangled
names to encode type information. g++ used to do this for all method types. It
now does it only for static method types. In any case, g++ now uses a new
mangling ABI. objdump doesn't know anything about the new ABI. So objdump
can't process the debugging information.
At least, that used to be true. I just checked in patches to objdump to
understand common cases of the new mangling ABI. objdump is now able to process
the stabs debugging information generated by current versions of g++, at least
in common cases such as the code in this PR. These patches to objdump will be
in the next GNU binutils release.
There is still a gcc issue, probably fixed by the recent patch in this PR, but I
believe that the main problem was in objdump.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7078