From: Michael Chastain <mec.gnu@mindspring.com>
To: kettenis@chello.nl, drow@false.org
Cc: jjohnstn@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: threaded watchpoint test
Date: Fri, 30 Jul 2004 00:55:00 -0000 [thread overview]
Message-ID: <41099C99.nail5DO11TT76@mindspring.com> (raw)
In-Reply-To: <200407292338.i6TNcNNY024581@elgar.kettenis.dyndns.org>
Mark Kettenis writes:
mark> Why do we allow tests like this to be checked in if we know they
mark> produce massive fails on many systems?
To take the philosophical question first: there's no registry of
which systems are actually tested with gdb. The list of posts to
gdb-testers@ is the only thing I have. If a system is not
represented there then I pay less attention to it.
Hmmm, this is in gdb.threads, I should not even have approved this
patch in the first place! I apologize to Michael Snyder.
mark> Hmm, I'm getting a bit frustrated that folks keep adding things to the
mark> testsuite that assume features that are not available on most things
mark> not i386 GNU/Linux.
I hear you.
Daniel Jacobowitz writes:
drow> Maybe not. It could be a bug to get a software watchpoint when we
drow> expect a hardware one. The question is whether we want to keep a
drow> separate list of "do we expect hardware watchpoints" in the testsuite.
I think so, but I'm not sure.
Two possible approaches are:
(1) The test suite does not keep its own info. The test suite asks
gdb whether gdb supports feature X, and trusts gdb.
(2) The test suite keeps separate info. That way, the test suite
is actually testing gdb, not just asking and trusting it.
But the info can get out of sync.
(2A) A whitelist of systems to test.
(2B) A blacklist of systems not to test.
I'm inclined to some form of (2). I don't like (1) because the test
suite is supposed to *test* gdb, not just trust gdb's answers.
Also, I don't know any existing gdb command to ask this question.
On the other hand, hardware watchpoints are not meant to work on
all systems, so it might be reasonable to ask gdb about them.
gdb.base/bigcore.exp is a big test that uses (2). First it blacklists
all the !isnative systems. Then it blacklists four specific systems:
bsd, hpux, solaris, cygwin.
For hardware watchpoint tests, the blacklist would be pretty long.
That's okay with me, it's just painful to set up the first time.
What do y'all think?
Michael C
next prev parent reply other threads:[~2004-07-30 0:55 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
2004-07-30 0:55 ` Michael Chastain [this message]
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=41099C99.nail5DO11TT76@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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