From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com, drow@false.org
Subject: Re: [testsuite] kfail sigaltstack.exp on i386/gnu/linux
Date: Sun, 08 Aug 2004 22:22:00 -0000 [thread overview]
Message-ID: <4116A794.nail8VF11ICCH@mindspring.com> (raw)
In-Reply-To: <20040808220220.GA22738@nevyn.them.org>
This patch is approved.
It's okay to use a KFAIL even for an external bug. The gdb PR can be
put in class "external" and refer to some external bug report against a
different product, and the gdb PR can still serve as a locus of
information about the bug.
===
2004-08-08 Daniel Jacobowitz <dan@debian.org>
PR gdb/1736
* gdb.base/sigaltstack.exp (finish_test): New procedure. KFAIL
for i?86-*-linux*.
next prev parent reply other threads:[~2004-08-08 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 22:02 Daniel Jacobowitz
2004-08-08 22:22 ` Michael Chastain [this message]
2004-08-08 23:14 ` Daniel Jacobowitz
2004-08-09 6:59 ` Michael Chastain
2004-08-09 17:15 ` Mark Kettenis
2004-08-09 17:30 ` Daniel Jacobowitz
2004-08-09 18:50 ` Michael Chastain
2004-08-09 17:27 ` 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=4116A794.nail8VF11ICCH@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--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