[PING] [PATCH v4 00/11] Add AlwaysNonStop remote protocol extension

"Bouhaouel, Mohamed" <[email protected]>
Newsgroups gmane.comp.gdb.patches
Message-ID <IA1PR11MB71756279AB5998D7B8C11CC2E4DE2@IA1PR11MB7175.namprd11.prod.outlook.com>
Kindly pinging :)

Thanks,

--Mohamed



________________________________
From: Mohamed Bouhaouel
Sent: Tuesday, July 14, 2026 11:21 AM
To: [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH v4 00/11] Add AlwaysNonStop remote protocol extension

From: "Bouhaouel, Mohamed" 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/[email protected]/ * V2 link: https://inbox.sourceware.org/gdb-patches/[email protected]/ * V1 link: https://inbox.sourceware.org/gdb-patches/[email protected]/ 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
________________________________________
Intel Deutschland GmbH 

Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany 

Tel: +49 (89) 99143-0 

www.intel.de 

Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran Sitaraman

Chairperson of the Supervisory Board: Sonja Pierer

Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB 186928

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.