This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/69785] c++filt can't demangle string or compiler produce wrong mangled string
- From: "trippels at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 15 Feb 2016 05:51:44 +0000
- Subject: [Bug debug/69785] c++filt can't demangle string or compiler produce wrong mangled string
- Auto-submitted: auto-generated
- References: <bug-69785-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69785
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-02-15
CC| |trippels at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Manuel LÃpez-IbÃÃez from comment #2)
> (In reply to Nikolay Piskun from comlibibertyment #1)
> > I can send a test program, but its rather long.
>
> Can gdb demangle it?
gdb uses the same libiberty demangler as the rest of the GNU tools.
The reporter said that c++filt can't demangle it, so of course gdb cannot
demangle it either.
And neither can Ian's go C++ demangler:
https://github.com/ianlancetaylor/demangle
So a test program would be welcome.