From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5892 invoked by alias); 15 Dec 2003 23:16:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5875 invoked from network); 15 Dec 2003 23:16:18 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sources.redhat.com with SMTP; 15 Dec 2003 23:16:18 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AW1wk-0008R8-00; Mon, 15 Dec 2003 18:16:14 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id D95F24B412; Mon, 15 Dec 2003 18:16:10 -0500 (EST) To: carlton@kealia.com, ian@wasabisystems.com Subject: Re: new demangler Cc: gdb@sources.redhat.com Message-Id: <20031215231610.D95F24B412@berman.michael-chastain.com> Date: Mon, 15 Dec 2003 23:16:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-12/txt/msg00221.txt.bz2 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