From: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
To: gdb-patches@sourceware.org
Cc: markus.t.metzger@intel.com, stephan.rohr@intel.com, eliz@gnu.org,
aburgess@redhat.com, pedro@palves.net
Subject: [PATCH v4 00/11] Add AlwaysNonStop remote protocol extension
Date: Tue, 14 Jul 2026 11:21:17 +0200 [thread overview]
Message-ID: <20260714092128.12941-1-mohamed.bouhaouel@intel.com> (raw)
From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
Hi,
This series introduces the AlwaysNonStop extension, enabling remote
stubs to declare preferable non-stop mode operation. When advertised,
GDB defaults to non-stop mode. Attempts to disable it might be rejected
by the stub with a descriptive error message.
The V1/V2 approach raised 'O' and 'F' packet compatibility concerns in
non-stop mode; this extension-based design addresses those risks
(discussed with Pedro Alves).
Key change from V3:
Relaxed the extension from a must target-non-stop to a prefer
target-non-stop. This will leave it the stub to decide if switching to
all-stop mode is allowed.
Additionally, added a gdbserver cli option, --enable-packet=PACKET, to
enable specific remote protocol packets or extensions at startup. Used
to add a test for the new 'AlwaysNonStop' extension.
Link to previous versions:
* V3 link: https://inbox.sourceware.org/gdb-patches/20260706121124.18784-1-mohamed.bouhaouel@intel.com/
* V2 link: https://inbox.sourceware.org/gdb-patches/20260611153232.3011-1-mohamed.bouhaouel@intel.com/
* V1 link: https://inbox.sourceware.org/gdb-patches/20260518183316.127043-1-mohamed.bouhaouel@intel.com/
Bouhaouel, Mohamed (8):
gdb, remote: fix assertion on reconnect to non-stop target
gdb, remote: fix async handler assertion on reconnect to non-stop
target
gdb, remote: fix "info program" after reconnect to non-stop target
gdb, remote: fix crash when accessing removed events
gdb, testsuite: handle async close in monitor-exit-quit.exp
gdb, testsuite: update attach-deleted-exec.exp to handle async
messages
gdb, testsuite: add kfails for step-over-process-exit.exp
gdb, gdbserver: add AlwaysNonStop remote protocol extension
Markus Metzger (1):
gdb, record: fix assertion when remote target is set to non-stop
Rohr, Stephan (2):
gdb, remote: fix ptid matching for process-wide stop events
gdb, dap: fix DAP events if no thread is selected
gdb/NEWS | 13 +++
gdb/doc/gdb.texinfo | 46 ++++++++++-
gdb/python/lib/gdb/dap/events.py | 15 +++-
gdb/record-full.c | 3 +-
gdb/remote.c | 68 ++++++++++++----
.../gdb.base/attach-deleted-exec.exp | 59 ++++++++------
.../gdb.server/enable-always-non-stop.exp | 56 +++++++++++++
.../gdb.server/monitor-exit-quit.exp | 21 ++++-
.../gdb.threads/step-over-process-exit.exp | 6 ++
gdbserver/server.cc | 79 +++++++++++++++++--
gdbserver/server.h | 2 +
gdbserver/target.cc | 6 ++
gdbserver/target.h | 6 ++
13 files changed, 328 insertions(+), 52 deletions(-)
create mode 100644 gdb/testsuite/gdb.server/enable-always-non-stop.exp
--
2.43.0
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2026-07-14 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:21 Mohamed Bouhaouel [this message]
2026-07-14 9:21 ` [PATCH v4 01/11] gdb, record: fix assertion when remote target is set to non-stop Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 02/11] gdb, remote: fix assertion on reconnect to non-stop target Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 03/11] gdb, remote: fix async handler " Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 04/11] gdb, remote: fix "info program" after " Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 05/11] gdb, remote: fix crash when accessing removed events Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 06/11] gdb, remote: fix ptid matching for process-wide stop events Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 07/11] gdb, dap: fix DAP events if no thread is selected Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 08/11] gdb, testsuite: handle async close in monitor-exit-quit.exp Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 09/11] gdb, testsuite: update attach-deleted-exec.exp to handle async messages Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 10/11] gdb, testsuite: add kfails for step-over-process-exit.exp Mohamed Bouhaouel
2026-07-14 9:21 ` [PATCH v4 11/11] gdb, gdbserver: add AlwaysNonStop remote protocol extension Mohamed Bouhaouel
2026-07-14 12:07 ` Eli Zaretskii
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=20260714092128.12941-1-mohamed.bouhaouel@intel.com \
--to=mohamed.bouhaouel@intel.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=pedro@palves.net \
--cc=stephan.rohr@intel.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