From: Tom Tromey <tom@tromey.com>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com,
stephan.rohr@intel.com, eliz@gnu.org, aburgess@redhat.com,
pedro@palves.net
Subject: Re: [PATCH v4 00/11] Add AlwaysNonStop remote protocol extension
Date: Fri, 04 Sep 2026 12:02:14 -0600 [thread overview]
Message-ID: <87jyp028ux.fsf@tromey.com> (raw)
In-Reply-To: <20260714092128.12941-1-mohamed.bouhaouel@intel.com> (Mohamed Bouhaouel's message of "Tue, 14 Jul 2026 11:21:17 +0200")
>>>>> Mohamed Bouhaouel <mohamed.bouhaouel@intel.com> writes:
> 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.
One thing I don't see in the series is the motivation for this.
It doesn't seem like something that would be useful to a user.
And if a server wants to work in all-stop-on-top-of-non-stop mode,
I don't think there's really anything preventing that; but also this
wouldn't require any kind of protocol extension.
I looked at this a little but I'm perhaps not the best person to review
it. I can take a stab at some of it at some point; but I would like to
understand the purpose.
thanks,
Tom
next prev parent reply other threads:[~2026-09-04 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:21 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
2026-09-04 18:02 ` Tom Tromey [this message]
2026-09-04 18:54 ` [PATCH v4 00/11] Add " Pedro Alves
2026-09-07 13:31 ` 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=87jyp028ux.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--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