From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tom@tromey.com>
Cc: Hannes Domani <ssbssa@yahoo.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] gdb/Windows: Fix detach while running
Date: Wed, 17 Apr 2024 19:18:36 +0100 [thread overview]
Message-ID: <8de61301-9692-40b1-ae52-3b58c79b5f75@palves.net> (raw)
In-Reply-To: <878r1e36gc.fsf@tromey.com>
I don't know why I forgot to reply to this part, sorry about that.
I had intended to. Correcting now.
On 2024-04-15 18:02, Tom Tromey wrote:
> I generally like the Windows debug API but I can't really understand why
> they didn't integrate WaitForDebugEvent with WaitForMultipleObjects --
> it seems like such an obvious thing to do and it would have saved so
> many headaches.
Totally agreed! It just seems so obvious. I even put that in a slide in my FOSDEM presentation this
last February:
https://fosdem.org/2024/schedule/event/fosdem-2024-2796-gdb-on-windows-status-plans/
https://fosdem.org/2024/events/attachments/fosdem-2024-2796-gdb-on-windows-status-plans/slides/22389/FOSDEM-2024-gdb-on-windows_IWzsEfL.pdf
Slides 22-25. Unfortunately I didn't have time to go through them in the actual talk.
If ever I have a chance of asking for debug features from MSFT, this will be one of them.
Pedro Alves
prev parent reply other threads:[~2024-04-17 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 20:03 [PATCH] " Pedro Alves
2024-04-12 10:56 ` Hannes Domani
2024-04-12 13:41 ` [PATCH v2] " Pedro Alves
2024-04-15 17:02 ` Tom Tromey
2024-04-17 17:57 ` Pedro Alves
2024-04-17 18:18 ` Pedro Alves [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=8de61301-9692-40b1-ae52-3b58c79b5f75@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).