From: Tom Tromey <tom@tromey.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: use all_threads() in for_each_thread()
Date: Wed, 13 May 2026 08:36:19 -0600 [thread overview]
Message-ID: <877bp7ml5o.fsf@tromey.com> (raw)
In-Reply-To: <20260512063244.2790197-1-markus.t.metzger@intel.com> (Markus Metzger's message of "Tue, 12 May 2026 06:32:44 +0000")
>>>>> "Markus" == Markus Metzger <markus.t.metzger@intel.com> writes:
Markus> In for_each_thread(), we use all_threads_safe(), which allows deleting the
Markus> thread. This it not needed in the cases where it is currently used and it
Markus> causes the iterator to get corrupted when threads are deleted in a nested
Markus> all_threads_safe() iteration.
Thanks, this is ok.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2026-05-13 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 6:32 Markus Metzger
2026-05-13 14:36 ` 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=877bp7ml5o.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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