From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Windows gdb: Avoid hang second attach/run
Date: Tue, 05 May 2026 08:05:47 -0600 [thread overview]
Message-ID: <87jytieytg.fsf@tromey.com> (raw)
In-Reply-To: <20260505121823.1442331-1-pedro@palves.net> (Pedro Alves's message of "Tue, 5 May 2026 13:18:23 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
Pedro> gdb.base/attach.exp starts a second inferior and tries to attach the
Pedro> second inferior to the same process that inferior 1 is already
Pedro> debugging. The point is to make sure that the backend errors out when
Pedro> it tries to attach to a process that is already being debugged.
Pedro> windows_nat_target::attach and windows_nat_target::create_inferior
Pedro> both hang in this situation, because they call into do_synchronously,
Pedro> which hangs because the 'process_thread' thread is blocked in
Pedro> WaitForDebugEvent.
Forgot the tag.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2026-05-05 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 12:18 Pedro Alves
2026-05-05 14:05 ` Tom Tromey
2026-05-07 18:24 ` Pedro Alves
2026-05-08 12:24 ` Tom Tromey
2026-05-05 14:05 ` 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=87jytieytg.fsf@tromey.com \
--to=tom@tromey.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