From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] KFAIL gdb.c++/annota2.exp watch triggered on a.x
Date: Fri, 03 Jan 2003 21:39:00 -0000 [thread overview]
Message-ID: <20030103213920.GA21687@nevyn.them.org> (raw)
In-Reply-To: <ro1ptrdlxvk.fsf@jackfruit.Stanford.EDU>
On Fri, Jan 03, 2003 at 01:35:59PM -0800, David Carlton wrote:
> Here's a patch to KFAIL the test "watch triggered on a.x" in
> gdb.c++/annota2.exp, corresponding to PR breakpoints/38. The test
> fails consistently on all the configurations that Michael tests.
>
> This is an obvious candidate for KFAILing. My only question is when
> it should currently be expected to pass. The PR indicates that it
> might pass on some platforms; on the other hand, it fails reliably
> on i686-pc-linux-gnu. So what I did was change the two existing
> instances of
>
> { pass "watch triggered on a.x" }
>
> to
>
> { setup_kfail "gdb/38" "i686*-*-*"
> pass "watch triggered on a.x" }
>
> but I made the new KFAIL case unconditional. That seemed to be the
> safest thing: that way, any FAIL or KPASS message is interesting.
May I recommend at the least "i?86"? Also, I really don't see the
point of the kpass's; before doing this, you need to establish if those
patterns are acceptable results; if so, they are passes, period.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-03 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 21:36 David Carlton
2003-01-03 21:39 ` Daniel Jacobowitz [this message]
2003-01-03 21:48 ` David Carlton
2003-01-03 21:51 ` Daniel Jacobowitz
2003-01-03 22:14 ` David Carlton
2003-01-03 22:30 ` Daniel Jacobowitz
2003-01-03 22:57 ` David Carlton
2003-01-09 17:10 ` David Carlton
2003-01-03 22:12 Michael Elizabeth Chastain
2003-01-03 22:27 ` David Carlton
2003-01-03 23:19 Michael Elizabeth Chastain
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=20030103213920.GA21687@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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