From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] New test sigbpt.{c,exp}
Date: Wed, 30 Jun 2004 18:53:00 -0000 [thread overview]
Message-ID: <20040630185321.C24534B104@berman.michael-chastain.com> (raw)
mec> Can you make more of the test names more unique?
ac> Oops, I thought I'd covered that. Try the attached.
It works for me.
All the test names are unique except for "rerun to main".
Stil the same four FAILs but that's okay because they really are FAILs.
I approve this patch.
ac> Are there [get_kernel_info] and [get_software_singlestep] testsuite calls?
I don't know of any.
I'm a bit leery of "get_kernel_info", because we should be testing
for features rather than version numbers (the whole autoconf philosophy).
Although get_compiler_info has worked reasonably well for the job
that it does.
I'm more inclined to dump a bunch of KFAIL's into the gdb_test_multiple
arms for the bad results, along with comments about which kernel versions
have been observed to have which behavior. Then in 3-5 years it's not
hard to sort out the obsolete crap.
If KFAIL's are too hard then just the comments for starters.
Michael C
===
2004-06-18 Andrew Cagney <cagney@gnu.org>
* gdb.base/sigbpt.exp, gdb.base/sigbpt.c: New test.
next reply other threads:[~2004-06-30 18:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 18:53 Michael Elizabeth Chastain [this message]
2004-07-06 15:10 ` Andrew Cagney
2004-07-06 15:35 ` Daniel Jacobowitz
2004-07-06 16:00 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 18:39 Michael Elizabeth Chastain
2004-07-06 18:59 Michael Elizabeth Chastain
2004-07-06 19:29 ` Andrew Cagney
2004-07-07 17:31 ` Andrew Cagney
2004-07-08 14:28 ` Daniel Jacobowitz
2004-07-06 18:12 Michael Elizabeth Chastain
2004-07-06 18:30 ` Daniel Jacobowitz
2004-06-30 3:53 Michael Elizabeth Chastain
2004-06-30 15:25 ` Andrew Cagney
2004-06-30 15:30 ` Daniel Jacobowitz
2004-07-02 13:24 ` Andrew Cagney
2004-06-29 23:44 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=20040630185321.C24534B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=ac131313@redhat.com \
--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