From: Tom Tromey <tom@tromey.com>
To: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
Cc: pedromfc@br.ibm.com, Ulrich.Weigand@de.ibm.com,
rogealve@br.ibm.com, Carl Love <cel@us.ibm.com>
Subject: Re: [PATCH] kill all threadapply processes at end of test
Date: Thu, 13 May 2021 09:44:49 -0600 [thread overview]
Message-ID: <87im3m63ke.fsf@tromey.com> (raw)
In-Reply-To: <e9d6547f4f9423c792ccadc926ca3240e94cc67e.camel@us.ibm.com> (Carl Love via Gdb-patches's message of "Wed, 12 May 2021 09:36:56 -0700")
>>>>> "Carl" == Carl Love via Gdb-patches <gdb-patches@sourceware.org> writes:
Carl> +# Make sure all of the threadapply processes are terminated
Carl> +set data [exec ps -e | grep threadapply]
This seems like an issue in a few ways. 'ps' arguments may differ by
platform. Other programs might be called 'threadapply' (unlikely for
user stuff but suppose I'm running 2 gdb test suites at the same time).
It doesn't handle cross-host testing (I don't know if we care about that
any more but in the past it was an issue).
So, I wonder if there's a better way to do this.
Like, could the test track PIDs itself? Then maybe re-attach?
thanks,
Tom
next prev parent reply other threads:[~2021-05-13 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 16:36 Carl Love via Gdb-patches
2021-05-13 14:30 ` Simon Marchi via Gdb-patches
2021-05-13 15:44 ` Tom Tromey [this message]
2021-05-13 18:10 ` Carl Love via Gdb-patches
2021-05-18 15:29 ` Carl Love via Gdb-patches
2021-05-18 21:56 ` Pedro Franco de Carvalho via Gdb-patches
2021-05-19 0:11 ` Pedro Franco de Carvalho via Gdb-patches
2021-05-20 15:42 ` Carl Love via Gdb-patches
2021-05-20 16:01 ` Carl Love via Gdb-patches
2021-05-24 15:30 ` Carl Love via Gdb-patches
2021-05-29 1:48 ` Simon Marchi via Gdb-patches
2021-06-01 15:42 ` Carl Love via Gdb-patches
2021-06-01 16:08 ` Simon Marchi via Gdb-patches
2021-06-02 15:08 ` Carl Love via Gdb-patches
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=87im3m63ke.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedromfc@br.ibm.com \
--cc=rogealve@br.ibm.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