From: Eli Zaretskii <eliz@gnu.org>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
Cc: gdb-patches@sourceware.org, stephan.rohr@intel.com,
markus.t.metzger@intel.com, pedro@palves.net,
aburgess@redhat.com
Subject: Re: [PATCH v3 11/11] gdb, gdbserver: add AlwaysNonStop remote protocol extension
Date: Mon, 06 Jul 2026 15:41:04 +0300 [thread overview]
Message-ID: <86zf0470kf.fsf@gnu.org> (raw)
In-Reply-To: <20260706121124.18784-12-mohamed.bouhaouel@intel.com> (message from Mohamed Bouhaouel on Mon, 6 Jul 2026 14:11:24 +0200)
> From: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
> Cc: stephan.rohr@intel.com, markus.t.metzger@intel.com, pedro@palves.net,
> aburgess@redhat.com
> Date: Mon, 6 Jul 2026 14:11:24 +0200
>
> From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
>
> Add a new RSP extension allowing remote stub to declare that a target
> must always 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 will reject QNonStop:0 requests
> * GDB errors if 'maint set target-non-stop off' is explicitly set
> ---
> gdb/NEWS | 8 ++++++++
> gdb/doc/gdb.texinfo | 30 +++++++++++++++++++++++++++++-
> gdb/remote.c | 27 +++++++++++++++++++++++++++
> gdbserver/server.cc | 30 +++++++++++++++++++++++++++++-
> gdbserver/target.cc | 6 ++++++
> gdbserver/target.h | 6 ++++++
> 6 files changed, 105 insertions(+), 2 deletions(-)
Thanks. The documentation parts are okay, with the following
comment:
> +@item @samp{E @var{nn}}
> +The request failed. This may occur if the stub requires non-stop mode
> +and advertised @samp{AlwaysNonStop+} support, and GDB attempted to
^^^
Should be @value{GDBN}
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2026-07-06 12:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 12:11 [PATCH v3 00/11] Add " Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 01/11] gdb, record: fix assertion when remote target is set to non-stop Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 02/11] gdb, remote: fix assertion on reconnect to non-stop target Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 03/11] gdb, remote: fix async handler " Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 04/11] gdb, remote: fix "info program" after " Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 05/11] gdb, remote: fix crash when accessing removed events Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 06/11] gdb, remote: fix ptid matching for process-wide stop events Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 07/11] gdb, dap: fix DAP events if no thread is selected Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 08/11] gdb, testsuite: handle async close in monitor-exit-quit.exp Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 09/11] gdb, testsuite: update attach-deleted-exec.exp to handle async messages Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 10/11] gdb, testsuite: add kfails for step-over-process-exit.exp Mohamed Bouhaouel
2026-07-06 12:11 ` [PATCH v3 11/11] gdb, gdbserver: add AlwaysNonStop remote protocol extension Mohamed Bouhaouel
2026-07-06 12:41 ` Eli Zaretskii [this message]
2026-07-14 9:28 ` Bouhaouel, Mohamed
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=86zf0470kf.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