From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, ian@wasabisystems.com
Cc: gdb@sources.redhat.com
Subject: Re: new demangler
Date: Mon, 15 Dec 2003 23:16:00 -0000 [thread overview]
Message-ID: <20031215231610.D95F24B412@berman.michael-chastain.com> (raw)
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
next reply other threads:[~2003-12-15 23:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 23:16 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 4:04 Michael Elizabeth Chastain
2003-12-15 23:55 Michael Elizabeth Chastain
2003-12-15 22:53 David Carlton
2003-12-15 22:54 ` Daniel Jacobowitz
2003-12-15 23:01 ` David Carlton
2003-12-15 23:10 ` Ian Lance Taylor
2003-12-15 23:17 ` David Carlton
2003-12-15 23:20 ` Ian Lance Taylor
2003-12-15 23:23 ` Ian Lance Taylor
2003-12-15 23:29 ` David Carlton
2003-12-15 23:33 ` Ian Lance Taylor
2003-12-15 23:38 ` David Carlton
2003-12-16 5:30 ` Daniel Jacobowitz
2003-12-18 2:22 ` Jim Blandy
2003-12-18 2:58 ` Ian Lance Taylor
2003-12-18 5:21 ` Daniel Jacobowitz
2003-12-18 16:01 ` 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=20031215231610.D95F24B412@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.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