From: Mark Kettenis <kettenis@chello.nl>
To: drow@false.org
Cc: mec.gnu@mindspring.com, jjohnstn@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFA]: threaded watchpoint test
Date: Thu, 29 Jul 2004 23:39:00 -0000 [thread overview]
Message-ID: <200407292338.i6TNcNNY024581@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040729152517.GA7192@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 29 Jul 2004 11:25:18 -0400)
Date: Thu, 29 Jul 2004 11:25:18 -0400
From: Daniel Jacobowitz <drow@false.org>
Sounds good to me. We'll probably want to clean up the other bit about
using the board_info too; or... just recognize that we got a software
watchpoint instead of a hardware one?
Maybe not. It could be a bug to get a software watchpoint when we
expect a hardware one. The question is whether we want to keep a
separate list of "do we expect hardware watchpoints" in the testsuite.
Hmm, I'm getting a bit frustrated that folks keep adding things to the
testsuite that assume features that are not available on most things
not i386 GNU/Linux.
Why do we allow tests like this to be checked in if we know they
produce massive fails on many systems?
Mark
next prev parent reply other threads:[~2004-07-29 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 18:56 Jeff Johnston
2004-07-27 22:56 ` Michael Chastain
2004-07-27 23:02 ` Daniel Jacobowitz
2004-07-27 23:24 ` Jeff Johnston
2004-07-27 23:27 ` Daniel Jacobowitz
2004-07-27 23:41 ` Jeff Johnston
2004-07-28 0:13 ` Michael Chastain
2004-07-29 15:26 ` Daniel Jacobowitz
2004-07-29 23:39 ` Mark Kettenis [this message]
2004-07-30 0:55 ` Michael Chastain
2004-07-30 22:33 ` Andrew Cagney
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=200407292338.i6TNcNNY024581@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.com \
--cc=mec.gnu@mindspring.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