From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdbsupport] Add sequential_for_each
Date: Fri, 15 Jul 2022 10:38:50 -0600 [thread overview]
Message-ID: <87r12mpbz9.fsf@tromey.com> (raw)
In-Reply-To: <20220625132042.GA31575@delia.com> (Tom de Vries via Gdb-patches's message of "Sat, 25 Jun 2022 15:20:44 +0200")
Tom> Add a sequential_for_each alongside the parallel_for_each, which can be used
Tom> as a drop-in replacement.
Tom> This can be useful when debugging multi-threading behaviour, and you want to
Tom> limit multi-threading in a fine-grained way.
It's not fine-grained but I typically just set the number of worker
threads to 0.
Tom
next prev parent reply other threads:[~2022-07-15 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 13:20 Tom de Vries
2022-07-14 15:02 ` [comitted][gdbsupport] " Tom de Vries
2022-07-15 16:38 ` Tom Tromey [this message]
2022-07-15 16:44 ` [PATCH][gdbsupport] " Tom de Vries
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=87r12mpbz9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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).