From: Andrew Cagney <ac131313@ges.redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Add xfail for i386 BSD's
Date: Wed, 10 Jul 2002 14:14:00 -0000 [thread overview]
Message-ID: <3D2CA1E0.90201@ges.redhat.com> (raw)
In-Reply-To: <200207041448.g64EmsU08483@elgar.kettenis.dyndns.org>
> I'm convinced this failure is caused by a kernel bug present on all
> i386 BSD's. Seen on FreeBSD and OpenBSD, and since OpenBSD is so
> similar to OpenBSD, I expect it to be "broken" too. The original
> BSD was already there, I just made sure the pattern catches the other
> ones too.
>
> Ok to check this in?
(I'm, for the moment, picking up more testsuite stuff for Fernando,
Fernando is concentrating on getting the KFAIL stuff resolved).
> Index: testsuite/ChangeLog
> from Mark Kettenis <kettenis@gnu.org>
>
> * gdb.base/interrupt.exp: Setup xfail for all i386 BSD's on "call
> function when asleep" test.
>
Yes (but I suspect that one of the above OpenBSDs was likely ment to be
NetBSD :-)
Andrew
next prev parent reply other threads:[~2002-07-10 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 8:03 Mark Kettenis
2002-07-10 14:14 ` Andrew Cagney [this message]
2002-07-10 16:09 ` Mark Kettenis
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=3D2CA1E0.90201@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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