From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [testsuite] Kfail signals.exp failures
Date: Mon, 09 Aug 2004 13:18:00 -0000 [thread overview]
Message-ID: <20040809131852.GD27539@nevyn.them.org> (raw)
In-Reply-To: <4117210E.nailSD2F36F9@mindspring.com>
On Mon, Aug 09, 2004 at 03:00:30AM -0400, Michael Chastain wrote:
> Daniel Jacobowitz <drow@false.org> wrote:
> > Andrew removed some "suspicious" xfails in signals.exp when he
> > overhauled it. They're a legitimate bug in GDB; I've put a complete
> > analysis in PR 1738. I expect all hardware single step targets to
> > fail; I maintained the previous list from the removed setup_xfails
> > (and added x86_64).
>
> Neat. This patch is approved.
Checked in. We may need to refine the target list later...
This covers most of the FAILs on my i686-pc-linux-gnu system. The
remaining are corefile.exp (blocked on vsyscall support);
null_record.exp (something has broken in GDB's debug info, maybe?);
and watchthread.exp (there's a bug in the test script, but I can't test
the patch, because it also triggers some internal bugs in GDB).
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-08-09 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 23:18 Daniel Jacobowitz
2004-08-09 7:00 ` Michael Chastain
2004-08-09 13:18 ` Daniel Jacobowitz [this message]
2004-08-09 7:46 ` Mark Kettenis
2004-08-09 13:11 ` Daniel Jacobowitz
2004-08-09 13:58 ` Andrew Cagney
2004-08-09 15:18 ` Daniel Jacobowitz
2004-08-09 16:17 ` Andrew Cagney
2004-08-09 16:44 ` Michael Chastain
2004-08-24 22:35 ` Andrew Cagney
2004-08-27 18:42 ` Mark Kettenis
2004-08-09 19:43 ` Andreas Schwab
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=20040809131852.GD27539@nevyn.them.org \
--to=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