This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: new demangler
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: carlton at kealia dot com, ian at wasabisystems dot com
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 15 Dec 2003 18:16:10 -0500 (EST)
- Subject: Re: new demangler
Works for me with c++filt.
[mec.gnu@berman migdmt]$ /berman/migchain/install/target/native/binutils-2.14/bin/c++filt _ZN1C6CClassaSERKS0_
C::CClass::operator=(C::CClass const&)
[mec.gnu@berman migdmt]$ echo _ZN1C6CClassaSERKS0_ | /berman/migchain/install/target/native/binutils-2.14/bin/c++filt
C::CClass::operator=(C::CClass const&)
[mec.gnu@berman migdmt]$ /berman/fsf/_current_/berman/install/target/native/binutils/HEAD/bin/c++filt _ZN1C6CClassaSERKS0_
C::CClass::operator=(C::CClass const&)
[mec.gnu@berman migdmt]$ echo _ZN1C6CClassaSERKS0_ | /berman/fsf/_current_/berman/install/target/native/binutils/HEAD/bin/c++filt
C::CClass::operator=(C::CClass const&)
One problem with talking about "the demangler" is that the options
parameter is different when the demangler is invoked in different ways.
c++filt uses different options for command line versus standard input,
and gdb specifies different options in different places.
Can you breakpoint cp_demangle inside gdb and see what's going on?
Michael C