From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow 'interrupt -a' in all-stop mode
Date: Mon, 13 Jun 2022 15:10:07 +0100 [thread overview]
Message-ID: <add50085-f6bd-a921-9538-f3a4d94659d8@palves.net> (raw)
In-Reply-To: <87y1y4y0qx.fsf@tromey.com>
On 2022-06-10 16:52, Tom Tromey wrote:
> +
> + You should have received a copy of the GNU General Public License
> + along with this program. If not, see <http://www.gnu.org/licenses/>. */
> +
> +#include <unistd.h>
> +
> +int
> +main ()
> +{
> + while (1)
> + sleep (50);
We try to avoid having testcases that run forever if GDB misbehaves. For more complicated
threading tests, we end up with something like:
/* Don't run forever. */
alarm (300);
For simpler testcases, we can just do something like:
int i;
for (i = 0; i < 60; i++)
sleep (1);
('i' should not be declared within the 'for' so that this compiles with
compilers that default to C89/C90.)
... which avoids introducing the depending on "alarm", which does not exist on all targets.
> +}
> diff --git a/gdb/testsuite/gdb.base/interrupt-a.exp b/gdb/testsuite/gdb.base/interrupt-a.exp
> new file mode 100644
> index 00000000000..9c65d6edd5f
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/interrupt-a.exp
> @@ -0,0 +1,50 @@
> +# Copyright (C) 2022 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
> +
> +# Test that 'interrupt -a' works in all stop mode.
> +
> +standard_testfile .c
> +set executable ${testfile}
> +
> +if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug}]} {
> + return -1
> +}
> +
> +if {![runto_main]} {
> + return -1
> +}
> +
> +set test "continue &"
> +gdb_test_multiple "continue&" $test {
> + -re "Continuing\\.\r\n$gdb_prompt " {
> + pass $test
> + }
> +}
You can get rid of the test variable (throughout) by using $gdb_test_name, like:
gdb_test_multiple "continue &" "" {
-re "Continuing\\.\r\n$gdb_prompt " {
pass $gdb_test_name
}
}
> +
> +set test "interrupt -a"
> +gdb_test_multiple $test $test {
> + -re "$gdb_prompt " {
> + pass $test
> + }
> +}
> +
> +after 200
This sleep normally appears after the "continue &" command, to give a bit of
time for the program to run after GDB prints "Continuing". Here, after an "interrupt"
command it doesn't appear necessary. I think you want to move it to right after
the continue command.
> +
> +set test "inferior stopped"
> +gdb_test_multiple "" $test {
> + -re "Program received signal" {
> + pass $test
> + }
> +}
>
Otherwise LGTM. Thanks.
next prev parent reply other threads:[~2022-06-13 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:27 Tom Tromey
2022-06-09 15:40 ` Pedro Alves
2022-06-10 15:52 ` Tom Tromey
2022-06-13 14:10 ` Pedro Alves [this message]
2022-06-14 15:04 ` 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=add50085-f6bd-a921-9538-f3a4d94659d8@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).