From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12762 invoked by alias); 25 Nov 2003 14:49:41 -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 12747 invoked from network); 25 Nov 2003 14:49:40 -0000 Received: from unknown (HELO mclean.mail.mindspring.net) (207.69.200.57) by sources.redhat.com with SMTP; 25 Nov 2003 14:49:40 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AOeVX-0001I5-00; Tue, 25 Nov 2003 09:49:39 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 9E1EC4B40A; Tue, 25 Nov 2003 09:49:50 -0500 (EST) To: carlton@kealia.com, gdb@sources.redhat.com, ian@wasabisystems.com Subject: Re: C++/Java regressions Message-Id: <20031125144950.9E1EC4B40A@berman.michael-chastain.com> Date: Tue, 25 Nov 2003 14:49:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-11/txt/msg00237.txt.bz2 Good morning, I see the same regressions that David does. This happened in all my gcc-3 configurations. If you want a specific configuration: target = native, host = i686-pc-linux-gnu, osversion = red-hat-8.0 gdb = HEAD 2003-11-25 04:21:57 UTC gcc = 3.3.2 binutils = 2.14 glibc = 2.2.93-5-rh gformat = dwarf-2 glevel = 2 I have two issues. === Issue #1: the demangler changed its interface. The demangler used to return parameters all the time, but now it looks like it returns parameters only if DMGL_PARAMS is given. This change did not happen with "complete rewrite". It happened with the followup patch: 2003-11-22 Ian Lance Taylor * cp-demangle.c (d_encoding): Add top_level parameter. Change all callers. (print_usage): Display new -p option. (long_options): Add --no-params. (main): Accept and handle -p. So the questions are: (A) Does gdb want to keep getting the parameters? (My answer: yes we do). (B) If we want the parameters, should we change gdb to set DMGL_PARAMS, or should we ask the demangler to keep giving us the parameters with our existing flags, which is usually just DMGL_ANSI? (My answer: let Ian tell us what the interface actually is, and then we'll adapt gdb to match). === Issue #2: "unsigned" versus "unsigned int" The new demangler prints "unsigned int" in some places where the old demangler prints "unsigned". This is fine. I updated gdb.cp/templates.exp to accept "unsigned int". Michael C