Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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:33 -0600	[thread overview]
Message-ID: <87o6iueytu.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> 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.

Do we need something similar for gdbserver?

Pedro> Until the Windows backend is taught to debug multiple processes, which
Pedro> will probably require having one process_thread thread per inferior,
Pedro> detect the situation and error out before GDB hangs.

Yeah.  I've never understood why MS did things this way instead of the
seemingly obvious approach of having debug events integrated into
WaitForMultipleObjects.

Pedro> There are still other failures not addressed by this patch.

FWIW the internal AdaCore automated testing shows a number of failures
after a merge on 20260427.  I guess when I did my testing I happened to
pick the one particular OS instance that had no problems :(

Tom

  reply	other threads:[~2026-05-05 14:06 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 [this message]
2026-05-07 18:24   ` Pedro Alves
2026-05-08 12:24     ` Tom Tromey
2026-05-05 14:05 ` 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=87o6iueytu.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