Re: [PATCH v4 11/11] gdb, gdbserver: add AlwaysNonStop remote protocol extension

Eli Zaretskii <[email protected]>
Newsgroups gmane.comp.gdb.patches
Message-ID <[email protected]>
> From: Mohamed Bouhaouel <[email protected]>
> Cc: [email protected],
> 	[email protected],
> 	[email protected],
> 	[email protected],
> 	[email protected]
> Date: Tue, 14 Jul 2026 11:21:28 +0200
> 
> From: "Bouhaouel, Mohamed" <[email protected]>
> 
> Add a new RSP extension allowing remote stubs to declare that a target
> prefers to operate in non-stop mode.
> 
> When a stub advertises "AlwaysNonStop+" in its qSupported response:
> 
> * The stub automatically initializes to non-stop mode.
> * GDB will operate the stub in non-stop mode (with default settings).
> * The stub may reject QNonStop:0 requests with descriptive error
>   messages.
> * GDB allows connection even if 'maint set target-non-stop off' is set,
>   but lets the stub decide whether to accept mode switches.
> 
> Additionally, gdbserver now accepts --enable-packet=PACKET to enable
> specific remote protocol packets or extensions at startup.  Currently
> this supports the 'AlwaysNonStop' extension.
> 
> Reviewed-By: Eli Zaretskii <[email protected]>
> ---
>  gdb/NEWS                                      | 13 +++
>  gdb/doc/gdb.texinfo                           | 46 ++++++++++-
>  gdb/remote.c                                  | 21 +++++
>  .../gdb.server/enable-always-non-stop.exp     | 56 +++++++++++++
>  gdbserver/server.cc                           | 79 +++++++++++++++++--
>  gdbserver/server.h                            |  2 +
>  gdbserver/target.cc                           |  6 ++
>  gdbserver/target.h                            |  6 ++
>  8 files changed, 223 insertions(+), 6 deletions(-)
>  create mode 100644 gdb/testsuite/gdb.server/enable-always-non-stop.exp

Thanks, the documentation parts are okay.

Reviewed-By: Eli Zaretskii <[email protected]>
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.