From: "Rohr, Stephan" <stephan.rohr@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/2] gdb: improve interrupting an empty remote target
Date: Mon, 17 Aug 2026 14:37:10 +0000 [thread overview]
Message-ID: <DS7PR11MB62471262AFFA3EAEE6143C5A93A72@DS7PR11MB6247.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20260805085919.218925-1-stephan.rohr@intel.com>
Kindly pinging 😊
> -----Original Message-----
> From: Stephan Rohr <stephan.rohr@intel.com>
> Sent: Wednesday, 5 August 2026 10:59
> To: gdb-patches@sourceware.org
> Subject: [PATCH 0/2] gdb: improve interrupting an empty remote target
>
> From: "Rohr, Stephan" <stephan.rohr@intel.com>
>
> Hello all,
>
> GDB hits an assertion when interrupting an empty remote target. Fix it
> by ensuring a valid thread first. We can also skip sending the 'vCont'
> package for an empty target. This is fixed in the second patch.
>
> Regression tested on Ubuntu 24 with the native, gdbserver and extended
> gdbserver targets.
>
> I appreciate your feedback.
>
> Thanks
> Stephan
>
> Rohr, Stephan (2):
> gdb: fix assertion when interrupting an empty remote target
> gdb, remote: Skip sending of 'vCont' package if remote target is empty
>
> gdb/infcmd.c | 5 +-
> gdb/remote.c | 4 ++
> .../interrupt-empty-remote-target.exp | 56 +++++++++++++++++++
> gdb/thread-iter.h | 3 +
> 4 files changed, 67 insertions(+), 1 deletion(-)
> create mode 100644 gdb/testsuite/gdb.server/interrupt-empty-remote-
> target.exp
>
> --
> 2.43.0
>
> ________________________________________
> Intel Deutschland GmbH
>
> Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
>
> Tel: +49 (89) 99143-0
>
> www.intel.de
>
> Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran
> Sitaraman
>
> Chairperson of the Supervisory Board: Sonja Pierer
>
> Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB
> 186928
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
________________________________________
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 (89) 99143-0
www.intel.de
Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran Sitaraman
Chairperson of the Supervisory Board: Sonja Pierer
Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB 186928
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
prev parent reply other threads:[~2026-08-17 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:59 Stephan Rohr
2026-08-05 8:59 ` [PATCH 1/2] gdb: fix assertion when " Stephan Rohr
2026-08-05 8:59 ` [PATCH 2/2] gdb, remote: Skip sending of 'vCont' package if remote target is empty Stephan Rohr
2026-08-17 14:37 ` Rohr, Stephan [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=DS7PR11MB62471262AFFA3EAEE6143C5A93A72@DS7PR11MB6247.namprd11.prod.outlook.com \
--to=stephan.rohr@intel.com \
--cc=gdb-patches@sourceware.org \
/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