From: Andrew Burgess <aburgess@redhat.com>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>,
gdb-patches@sourceware.org
Cc: mohamed.bouhaouel@intel.com, stephan.rohr@intel.com,
markus.t.metzger@intel.com
Subject: Re: [PATCH 01/11] gdb, record: fix assertion when remote target is set to non-stop
Date: Wed, 10 Jun 2026 16:48:39 +0100 [thread overview]
Message-ID: <874ijaqtuw.fsf@redhat.com> (raw)
In-Reply-To: <20260518183316.127043-2-mohamed.bouhaouel@intel.com>
Mohamed Bouhaouel <mohamed.bouhaouel@intel.com> writes:
> From: Markus Metzger <markus.t.metzger@intel.com>
>
> When forcing the remote target to non-stop via 'maint set target-non-stop
> on', reverse tests start failing with
>
> (gdb) .../gdb/remote.c:7561: internal-error: resume: Assertion `scope_ptid == inferior_ptid' failed.
>
> This is caused by the record-full target doing one additional step after
> receiving a single-step trap event. That additional step is done on the
> wait ptid instead of on the event ptid. Fix it.
> ---
> gdb/record-full.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
I notice there's no new test here.
My guess is that this fixes an issue that will show up in some test once
patch #11 is merged. Please could you include the details of which test
exposes this issue so it's easy to review this patch.
I've had a look at the next couple of patches and I think this same
feedback applies to them to. I suspect (but have not checked) this
probably applies to patches #1 to #10.
Thanks,
Andrew
>
> diff --git a/gdb/record-full.c b/gdb/record-full.c
> index 69d2c100e57..fbb45c84931 100644
> --- a/gdb/record-full.c
> +++ b/gdb/record-full.c
> @@ -1290,7 +1290,8 @@ record_full_wait_1 (struct target_ops *ops,
> "Process record: record_full_wait "
> "issuing one more step in the "
> "target beneath\n");
> - ops->beneath ()->resume (ptid, step, GDB_SIGNAL_0);
> + ops->beneath ()->resume (inferior_ptid, step,
> + GDB_SIGNAL_0);
> proc_target->commit_resumed_state = true;
> proc_target->commit_resumed ();
> proc_target->commit_resumed_state = false;
> --
> 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
next prev parent reply other threads:[~2026-06-10 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 18:32 [PATCH 00/11] Enable non-stop mode by default for remote targets Mohamed Bouhaouel
2026-05-18 18:32 ` [PATCH 01/11] gdb, record: fix assertion when remote target is set to non-stop Mohamed Bouhaouel
2026-06-10 15:48 ` Andrew Burgess [this message]
2026-06-11 15:50 ` Bouhaouel, Mohamed
2026-05-18 18:32 ` [PATCH 02/11] gdb, remote: fix assertion on reconnect to non-stop target Mohamed Bouhaouel
2026-05-18 18:32 ` [PATCH 03/11] gdb, remote: fix async handler " Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 04/11] gdb, remote: fix "info program" after " Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 05/11] gdb, remote: fix crash when accessing removed events Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 06/11] gdb, remote: fix ptid matching for process-wide stop events Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 07/11] gdb, dap: fix DAP events if no thread is selected Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 08/11] gdb, testsuite: handle async close in monitor-exit-quit.exp Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 09/11] gdb, testsuite: update attach-deleted-exec.exp to handle async messages Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 10/11] gdb, testsuite: add kfails for step-over-process-exit.exp Mohamed Bouhaouel
2026-05-18 18:33 ` [PATCH 11/11] gdb, remote: implement always_non_stop_p for remote target Mohamed Bouhaouel
2026-06-10 11:44 ` PING 01 - [PATCH 00/11] Enable non-stop mode by default for remote targets Bouhaouel, Mohamed
2026-06-12 14:20 ` Pedro Alves
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=874ijaqtuw.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=mohamed.bouhaouel@intel.com \
--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