From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6985 invoked by alias); 15 Dec 2003 23:17:36 -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 6963 invoked from network); 15 Dec 2003 23:17:35 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 15 Dec 2003 23:17:35 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id A72A6C6C3; Mon, 15 Dec 2003 15:17:33 -0800 (PST) To: Ian Lance Taylor Cc: gdb Subject: Re: new demangler References: <20031215225452.GA23169@nevyn.them.org> From: David Carlton Date: Mon, 15 Dec 2003 23:17:00 -0000 In-Reply-To: (Ian Lance Taylor's message of "15 Dec 2003 18:10:36 -0500") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-12/txt/msg00222.txt.bz2 On 15 Dec 2003 18:10:36 -0500, Ian Lance Taylor said: > `maint demangle' only works for me when I explicitly run gdb on a > C++ program. When I do specify a C++ program, it appears to work > correctly. Ah, I see. Now I'm getting it to work correctly with 'maint demangle', too. So is there a problem with the way class_name_from_physname invokes the demangler? It does this: char *demangled_name = cplus_demangle (physname, DMGL_ANSI); Compared to other places in GDB where the demangler is called, this is unusual since DMGL_PARAMS isn't passed in as well, but I don't see why that would cause the demangling to fail completely. David Carlton carlton@kealia.com