From: Tom de Vries <tdevries@suse.de>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org, John Baldwin <jhb@FreeBSD.org>
Subject: Re: [PATCH 2/2] [gdb] Exclude unavailable hardware threads in default worker-threads
Date: Wed, 16 Sep 2026 19:27:23 +0200 [thread overview]
Message-ID: <c5967674-18d1-49ed-9598-02e92c229e86@suse.de> (raw)
In-Reply-To: <e231c77c-e90e-4907-abea-f9b977f87e8b@suse.de>
On 9/9/26 2:02 PM, Tom de Vries wrote:
> On 9/7/26 6:44 AM, Thiago Jung Bauermann wrote:
>> his is a nice improvement. At least some good came out of my red
>> herring. Thanks!
>>
>> One comment, but:
>>
>> Reviewed-by: Thiago Jung Bauermann<thiago.bauermann@linaro.org>
>
> I'm hoping to find time to get this working as well for (some
> compatibility setups for) Windows before committing.
>
I tried out msys2, and the problem didn't reproduce there when using
taskset. There's a windows native tool called start that I tried as
well, but I didn't get it to work.
The problem did reproduce with cygwin, and the solution was to just use
the same fix for __CYGWIN__ as for __linux___, so I've committed that.
Thanks,
- Tom
> I used to have a freebsd setup on my laptop, but a fedora update has
> rendered it unbootable, so I'll skip that for now.
>
> Thanks,
> - Tom
next prev parent reply other threads:[~2026-09-16 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 15:48 [PATCH 1/2] [gdb/testsuite] Fix timeout in do_self_tests Tom de Vries
2026-09-06 15:48 ` [PATCH 2/2] [gdb] Exclude unavailable hardware threads in default worker-threads Tom de Vries
2026-09-07 4:44 ` Thiago Jung Bauermann
2026-09-07 6:52 ` Tom de Vries
2026-09-09 12:02 ` Tom de Vries
2026-09-16 17:27 ` Tom de Vries [this message]
2026-09-07 4:36 ` [PATCH 1/2] [gdb/testsuite] Fix timeout in do_self_tests Thiago Jung Bauermann
2026-09-09 11:57 ` Tom de Vries
2026-09-09 20:28 ` Thiago Jung Bauermann
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=c5967674-18d1-49ed-9598-02e92c229e86@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=thiago.bauermann@linaro.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