From: Tom Tromey <tromey@adacore.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow 'interrupt -a' in all-stop mode
Date: Tue, 14 Jun 2022 09:04:02 -0600 [thread overview]
Message-ID: <87tu8nxp5p.fsf@tromey.com> (raw)
In-Reply-To: <add50085-f6bd-a921-9538-f3a4d94659d8@palves.net> (Pedro Alves's message of "Mon, 13 Jun 2022 15:10:07 +0100")
Pedro> We try to avoid having testcases that run forever if GDB
Pedro> misbehaves. For more complicated threading tests, we end up with
Pedro> something like:
[...]
Thanks, I fixed this & the other comments.
I'm going to check it in now.
Tom
prev parent reply other threads:[~2022-06-14 15:04 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
2022-06-14 15:04 ` Tom Tromey [this message]
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=87tu8nxp5p.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).