From: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
To: gdb-patches@sourceware.org
Cc: stephan.rohr@intel.com, markus.t.metzger@intel.com,
pedro@palves.net, aburgess@redhat.com
Subject: [PATCH v3 05/11] gdb, remote: fix crash when accessing removed events
Date: Mon, 6 Jul 2026 14:11:18 +0200 [thread overview]
Message-ID: <20260706121124.18784-6-mohamed.bouhaouel@intel.com> (raw)
In-Reply-To: <20260706121124.18784-1-mohamed.bouhaouel@intel.com>
From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
Dereferencing events after calling std::remove_if causes GDB to crash
because the matching unique_ptrs have been moved from and are null.
Fix by logging events in std::remove_if.
The bug is visible by inspection; reproducing it requires
discard_pending_stop_replies to be called with matching entries in the
queue and remote debug logging enabled.
---
gdb/remote.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/gdb/remote.c b/gdb/remote.c
index f6178caf7a1..323edd6cb0f 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -8254,17 +8254,20 @@ remote_target::discard_pending_stop_replies (struct inferior *inf)
/* Discard the stop replies we have already pulled with
vStopped. */
- auto iter = std::remove_if (rs->stop_reply_queue.begin (),
- rs->stop_reply_queue.end (),
- [=] (const stop_reply_up &event)
- {
- return event->ptid.pid () == inf->pid;
- });
- for (auto it = iter; it != rs->stop_reply_queue.end (); ++it)
- remote_debug_printf
- ("discarding queued stop reply: ptid: %s, ws: %s\n",
- (*it)->ptid.to_string().c_str(),
- (*it)->ws.to_string ().c_str ());
+ auto iter
+ = std::remove_if (rs->stop_reply_queue.begin (),
+ rs->stop_reply_queue.end (),
+ [=] (const stop_reply_up &event)
+ {
+ if (event->ptid.pid () != inf->pid)
+ return false;
+
+ remote_debug_printf
+ ("discarding queued stop reply: ptid: %s, ws: %s\n",
+ event->ptid.to_string ().c_str (),
+ event->ws.to_string ().c_str ());
+ return true;
+ });
rs->stop_reply_queue.erase (iter, rs->stop_reply_queue.end ());
}
--
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-07-06 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 12:11 [PATCH v3 00/11] Add AlwaysNonStop remote protocol extension 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 ` Mohamed Bouhaouel [this message]
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
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=20260706121124.18784-6-mohamed.bouhaouel@intel.com \
--to=mohamed.bouhaouel@intel.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@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