From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28485 invoked by alias); 25 Nov 2003 17:59:09 -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 28478 invoked from network); 25 Nov 2003 17:59:08 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 25 Nov 2003 17:59:08 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AOhSt-0006bl-V0 for ; Tue, 25 Nov 2003 12:59:07 -0500 Date: Tue, 25 Nov 2003 17:59:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: C++/Java regressions Message-ID: <20031125175907.GA21416@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <20031125170632.D8D974B409@berman.michael-chastain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-11/txt/msg00245.txt.bz2 On Tue, Nov 25, 2003 at 09:14:31AM -0800, David Carlton wrote: > On Tue, 25 Nov 2003 12:06:32 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said: > > > I asked: > > mec> What is the correct output when a breakpoint is taken on > mec> "A::bar(int) const" ? > > Probably my first choice would be A::bar(int) const, and my second > choice would be A::bar. A::bar const seems a bit weird to me. Having > said that: > > > After some deliberation, I decided that I want the test script > > to be liberal in what it accepts. > ... > > If someone wants to spend time on making gdb's output better here, > > that is okay with me. But I decided that it's too low priority for > > my attention and the list bandwidth. > > > David C is that okay with you? > > Yes, that's fine with me. What is important is that the breakpoint be > set on the correct method, and that the continue reach the correct > breakpoint. That is in fact happening; I don't really see the point > of having a failing test there, or even a kfailing test. This works for me too. Meanwhile, fixing DMGL_PARAMS not to print the trailing const seems like a reasonable change. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer