From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: C++/Java regressions
Date: Tue, 25 Nov 2003 17:59:00 -0000 [thread overview]
Message-ID: <20031125175907.GA21416@nevyn.them.org> (raw)
In-Reply-To: <yf2ekvwv094.fsf@hawaii.kealia.com>
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
next prev parent reply other threads:[~2003-11-25 17:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 17:06 Michael Elizabeth Chastain
2003-11-25 17:14 ` David Carlton
2003-11-25 17:59 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 22:48 Michael Elizabeth Chastain
2003-11-26 21:44 Michael Elizabeth Chastain
2003-11-26 22:21 ` Ian Lance Taylor
2003-11-26 22:28 ` Daniel Jacobowitz
2003-11-26 22:34 ` Ian Lance Taylor
2003-11-26 21:18 Michael Elizabeth Chastain
2003-11-26 21:33 ` Ian Lance Taylor
2003-11-25 15:33 Michael Elizabeth Chastain
2003-11-25 14:49 Michael Elizabeth Chastain
2003-11-25 15:06 ` Daniel Jacobowitz
2003-11-25 4:44 Michael Elizabeth Chastain
2003-11-25 17:54 ` Ian Lance Taylor
2003-11-25 1:37 David Carlton
2003-11-25 3:58 ` Ian Lance Taylor
2003-11-26 4:04 ` Ian Lance Taylor
2003-11-26 15:32 ` Daniel Jacobowitz
2003-11-26 21:05 ` Ian Lance Taylor
2003-11-26 21:11 ` David Carlton
2003-11-26 21:12 ` Daniel Jacobowitz
2003-11-26 21:32 ` Ian Lance Taylor
2003-12-01 16:45 ` Daniel Jacobowitz
2003-11-30 2:57 ` Jim Blandy
2003-11-30 3:12 ` Daniel Jacobowitz
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=20031125175907.GA21416@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.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