From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Hui Zhu <teawater@gmail.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Make the prec support signal better[0/4]
Date: Thu, 10 Sep 2009 23:30:00 -0000 [thread overview]
Message-ID: <20090910232952.GP20694@adacore.com> (raw)
In-Reply-To: <4AA95648.10605@vmware.com>
> Attached is a test case for it -- it will have a number of
> XFAILS without this patch, which will become PASSES with the patch.
I looked at the testcase, and noticed a couple of things:
> # Copyright 1995, 1996, 1997, 1999, 2007, 2008, 2009
I was surprised by the copyright years, but I then read the contents
of the testcase that mentions alpha-osf3. That's when I realized
that this file is inspired by sigall.exp... I supposed that this
was the right thing to do, although it probably does not matter
because I believe that these headers are actually not legally
significant.
> if [target_info exists gdb,nosignals] {
> verbose "Skipping sigall-reverse.exp because of nosignals."
> continue
> }
I wonder why we do a continue here, whereas we do a return elsewhere:
> if ![target_info exists gdb,can_reverse] {
> return
> }
I wish we had a cookbook for writing testcases, I always forget what
we're supposed to do :-(. Anyone knows if this is significant?
> send_gdb "continue\n"
> if { $thissig == "IO" } {
> setup_xfail "i*86-pc-linuxoldld-gnu" "i*86-pc-linuxaout-gnu"
> }
> gdb_expect {
[...]
IMO, the send_gdb/gdb_expect sequences in this script should be converted
to using test_gdb_multiple. I'd rather we avoid send_gdb/gdb_expect
if we can.
--
Joel
next prev parent reply other threads:[~2009-09-10 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 13:28 Hui Zhu
2009-09-10 19:43 ` Michael Snyder
2009-09-10 23:30 ` Joel Brobecker [this message]
2009-09-11 0:30 ` Michael Snyder
2009-09-11 20:07 ` Michael Snyder
2009-09-11 23:43 ` Joel Brobecker
2009-09-12 0:43 ` Michael Snyder
2009-09-12 1:02 ` Joel Brobecker
2009-09-13 0:29 ` Michael Snyder
2009-09-11 21:52 ` Tom Tromey
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=20090910232952.GP20694@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.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