From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Remove for_each_thread
Date: Thu, 14 May 2026 11:48:58 -0600 [thread overview]
Message-ID: <87ik8pkhkl.fsf@tromey.com> (raw)
In-Reply-To: <9c0a15ea-df3d-4795-9028-f290fdeb8232@simark.ca> (Simon Marchi's message of "Thu, 14 May 2026 10:13:31 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> Perhaps mention that there is a functional change, since you switch from
Simon> using all_threads_safe to all_threads everywhere. This happens to fix
Simon> the bug that Markus was fixing here:
Simon> https://inbox.sourceware.org/gdb-patches/20260504071636.1571615-2-markus.t.metzger@intel.com/
I was actually assuming I'd end up rebasing my patch on top of his when
it lands.
Tom
next prev parent reply other threads:[~2026-05-14 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 17:32 [PATCH 0/2] " Tom Tromey
2026-05-13 17:32 ` [PATCH 1/2] Use bool in continue_1 Tom Tromey
2026-05-14 14:00 ` Simon Marchi
2026-05-13 17:32 ` [PATCH 2/2] Remove for_each_thread Tom Tromey
2026-05-14 14:13 ` Simon Marchi
2026-05-14 17:48 ` Tom Tromey [this message]
2026-07-22 18:21 ` [PATCH 0/2] " 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=87ik8pkhkl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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