From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 00/11] Windows non-stop mode
Date: Wed, 29 Apr 2026 21:14:56 +0100 [thread overview]
Message-ID: <20260429201507.480870-1-pedro@palves.net> (raw)
Here is the third iteration of the Windows non-stop work.
I've pushed the series to the users/palves/windows-non-stop-v3 branch
on sourceware.org, for your convenience.
Compared to the previous version, here:
https://inbox.sourceware.org/gdb-patches/20250519132308.3553663-1-pedro@palves.net
... this one is much smaller, as most of the preparatory changes have
been merged already. For the patches that still remain, not much has
changed, other than rebasing and resolving conflicts, and addressing a
couple minor review comments.
I've added "Approved-By:" tags from last year's review.
Here's the original intro blurb, still accurate:
This series adds non-stop mode support to the Windows native backend,
on Windows 10 and above. Earlier Windows versions lack the necessary
feature, so those keep working in all-stop mode, only.
After the series, the Windows target backend defaults to working in
non-stop mode (as in, "maint set target-non-stop"), even if
user-visible mode is all-stop ("set non-stop off"). This is the same
as the Linux backend.
I've been testing this on Cygwin native with the GDB testsuite as I've
been developing this. Running the testsuite on Cygwin is a pain, and
many testcases run into cascading timeouts still, and some even hang
the test run forever until you kill them manually. I've got another
series of patches to improve such tests and skip others, and that's
what I've been testing with. I've also tested the series with the
windows-nat backend forced to all-stop mode.
Pedro Alves (11):
Windows gdb+gdbserver: Check whether DBG_REPLY_LATER is available
linux-nat: Factor out get_detach_signal code to common code
Windows GDB: make windows_thread_info be private thread_info data
Introduce windows_nat::event_code_to_string
Windows gdb: Add non-stop support
Windows gdb: Watchpoints while running (internal vs external stops)
Windows gdb: extra thread info => show exiting
Add gdb.threads/leader-exit-schedlock.exp
infrun: with AS+NS, prefer process exit over thread exit
Windows gdb: Always non-stop (default to "maint set target-non-stop
on")
Mention Windows non-stop support in NEWS
gdb/NEWS | 3 +
gdb/aarch64-windows-nat.c | 13 +-
gdb/infrun.c | 246 +++-
gdb/infrun.h | 6 +
gdb/linux-nat.c | 41 +-
gdb/nat/windows-nat.c | 62 +-
gdb/nat/windows-nat.h | 83 +-
gdb/target/waitstatus.h | 4 +-
.../gdb.threads/leader-exit-schedlock.c | 56 +
.../gdb.threads/leader-exit-schedlock.exp | 215 +++
.../gdb.threads/step-over-process-exit.c | 49 +
.../gdb.threads/step-over-process-exit.exp | 66 +
gdb/windows-nat.c | 1285 ++++++++++++++---
gdb/windows-nat.h | 142 +-
gdb/x86-windows-nat.c | 16 +-
gdbserver/win32-low.cc | 60 +-
gdbserver/win32-low.h | 4 +-
17 files changed, 1973 insertions(+), 378 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/leader-exit-schedlock.c
create mode 100644 gdb/testsuite/gdb.threads/leader-exit-schedlock.exp
create mode 100644 gdb/testsuite/gdb.threads/step-over-process-exit.c
create mode 100644 gdb/testsuite/gdb.threads/step-over-process-exit.exp
base-commit: 5ed455efd8476ce4f70266d5797ef9f3eb1e8919
--
2.53.0
next reply other threads:[~2026-04-29 20:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 20:14 Pedro Alves [this message]
2026-04-29 20:14 ` [PATCH v3 01/11] Windows gdb+gdbserver: Check whether DBG_REPLY_LATER is available Pedro Alves
2026-04-29 20:14 ` [PATCH v3 02/11] linux-nat: Factor out get_detach_signal code to common code Pedro Alves
2026-04-29 20:14 ` [PATCH v3 03/11] Windows GDB: make windows_thread_info be private thread_info data Pedro Alves
2026-04-29 20:15 ` [PATCH v3 04/11] Introduce windows_nat::event_code_to_string Pedro Alves
2026-04-29 20:15 ` [PATCH v3 05/11] Windows gdb: Add non-stop support Pedro Alves
2026-04-29 20:15 ` [PATCH v3 06/11] Windows gdb: Watchpoints while running (internal vs external stops) Pedro Alves
2026-04-29 20:15 ` [PATCH v3 07/11] Windows gdb: extra thread info => show exiting Pedro Alves
2026-04-29 20:15 ` [PATCH v3 08/11] Add gdb.threads/leader-exit-schedlock.exp Pedro Alves
2026-04-29 20:15 ` [PATCH v3 09/11] infrun: with AS+NS, prefer process exit over thread exit Pedro Alves
2026-05-06 10:01 ` Bouhaouel, Mohamed
2026-05-08 21:37 ` Pedro Alves
2026-05-11 11:58 ` Bouhaouel, Mohamed
2026-04-29 20:15 ` [PATCH v3 10/11] Windows gdb: Always non-stop (default to "maint set target-non-stop on") Pedro Alves
2026-04-29 20:15 ` [PATCH v3 11/11] Mention Windows non-stop support in NEWS Pedro Alves
2026-04-30 5:55 ` [PATCH v3 00/11] Windows non-stop mode Eli Zaretskii
2026-04-30 10:13 ` Pedro Alves
2026-04-30 11:14 ` Eli Zaretskii
2026-04-30 12:01 ` Pedro Alves
2026-04-30 14:15 ` [PATCH] Clarify "maint set target-non-stop" in GDB manual (Re: [PATCH v3 00/11] Windows non-stop mode) Pedro Alves
2026-04-30 15:09 ` Eli Zaretskii
2026-04-30 16:18 ` [PATCH v2] " Pedro Alves
2026-04-30 16:27 ` Eli Zaretskii
2026-04-30 16:33 ` Pedro Alves
2026-04-30 17:45 ` [PATCH v3 00/11] Windows non-stop mode Pedro Alves
2026-05-08 18:43 ` Tom Tromey
2026-05-08 21:27 ` Pedro Alves
2026-05-22 0:22 ` Pedro Alves
2026-06-02 19:00 ` 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=20260429201507.480870-1-pedro@palves.net \
--to=pedro@palves.net \
--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