Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com,
	stephan.rohr@intel.com, aburgess@redhat.com, pedro@palves.net
Subject: Re: [PATCH v4 11/11] gdb, gdbserver: add AlwaysNonStop remote protocol extension
Date: Tue, 14 Jul 2026 15:07:42 +0300	[thread overview]
Message-ID: <86ech5g4fl.fsf@gnu.org> (raw)
In-Reply-To: <20260714092128.12941-12-mohamed.bouhaouel@intel.com> (message from Mohamed Bouhaouel on Tue, 14 Jul 2026 11:21:28 +0200)

> From: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
> Cc: markus.t.metzger@intel.com,
> 	stephan.rohr@intel.com,
> 	eliz@gnu.org,
> 	aburgess@redhat.com,
> 	pedro@palves.net
> Date: Tue, 14 Jul 2026 11:21:28 +0200
> 
> From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
> 
> 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 <eliz@gnu.org>
> ---
>  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 <eliz@gnu.org>

      reply	other threads:[~2026-07-14 12:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  9:21 [PATCH v4 00/11] Add " Mohamed Bouhaouel
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 [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=86ech5g4fl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=mohamed.bouhaouel@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