From: Andrew Burgess <aburgess@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Guard against killing unrelated processes in amd64-disp-step.exp
Date: Sat, 15 Jul 2023 14:38:51 +0100 [thread overview]
Message-ID: <875y6li9as.fsf@redhat.com> (raw)
In-Reply-To: <yddfs5srrc4.fsf@CeBiTec.Uni-Bielefeld.DE>
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> When testing current gdb trunk on Solaris/amd64, the whole session was
> reliably terminated by make check. I could trace this to the following
> entry in gdb.arch/amd64-disp-step/gdb.log:
>
> FAIL: gdb.arch/amd64-disp-step.exp: add into rcx: send_signal=on: get inferior pid
> Executing on target: kill -ALRM -1 (timeout = 300)
> builtin_spawn -ignore SIGHUP kill -ALRM -1
>
> If $inferior_pid doesn't refer a single process for some reason, this
> kill would terminate either a process group or the whole session.
>
> This patch avoids this by ensuring that the pid arg is positive.
>
> Tested on amd64-pc-solaris2.11 and x86_64-pc-linux-gnu.
>
> Ok for trunk?
>
> Rainer
>
> --
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University
>
>
> diff --git a/gdb/testsuite/gdb.arch/amd64-disp-step.exp b/gdb/testsuite/gdb.arch/amd64-disp-step.exp
> --- a/gdb/testsuite/gdb.arch/amd64-disp-step.exp
> +++ b/gdb/testsuite/gdb.arch/amd64-disp-step.exp
> @@ -222,7 +222,10 @@ proc rip_test { reg test_start_label tes
> # If we use 'signal' to send the signal GDB doesn't actually do
> # the displaced step, but instead just delivers the signal.
> set inferior_pid [get_inferior_pid]
> - remote_exec target "kill -ALRM $inferior_pid"
> + # Ensure that $inferior_pid refers to a single process.
> + if {$inferior_pid > 0} {
> + remote_exec target "kill -ALRM $inferior_pid"
> + }
Does this not hide the fact that the test is no longer doing what it
expected?
I'm fine with the 'if {$inferior_pid > 0}' being added to ensure we
don't signal some random process(es), but I think we should probably add
something like:
gdb_assert {[expr $inferior_pid > 0]} \
"check for a sane inferior pid"
if {$inferior_pid > 0} {
remote_exec target "kill -ALRM $inferior_pid"
}
This way you will still see a FAIL.
Thoughts?
Thanks,
Andrew
next prev parent reply other threads:[~2023-07-15 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 11:19 Rainer Orth
2023-07-13 16:34 ` Tom Tromey
2023-07-13 17:59 ` Rainer Orth
2023-07-14 17:25 ` Pedro Alves
2023-07-19 12:21 ` Rainer Orth
2023-07-15 13:38 ` Andrew Burgess [this message]
2023-07-19 12:37 ` Rainer Orth
2023-08-01 14:05 ` Rainer Orth
2023-08-02 20:56 ` Tom Tromey
2023-08-07 13:51 ` Rainer Orth
2023-08-07 22:14 ` 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=875y6li9as.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).