Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stephan Rohr <stephan.rohr@intel.com>
To: gdb-patches@sourceware.org
Cc: guinevere@redhat.com
Subject: [PATCH v2 0/1] gdb: fix assert after register write failure
Date: Thu, 15 Oct 2026 14:11:26 +0000	[thread overview]
Message-ID: <20261015141127.152846-1-stephan.rohr@intel.com> (raw)

From: "Rohr, Stephan" <stephan.rohr@intel.com>

Hi all,

this is v2 of the patch.

v1 of the patch is available here:
https://sourceware.org/pipermail/gdb-patches/2026-October/230972.html

Guinevere provided feedback:
https://sourceware.org/pipermail/gdb-patches/2026-October/231104.html

Changes since v1:

  - Moved nullptr check to regcache::invalidate ().

Thanks
Stephan

Eduard Sargsyan (1):
  gdb: fix assert after register write failure

 gdb/regcache.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

-- 
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.


             reply	other threads:[~2026-10-15 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 14:11 Stephan Rohr [this message]
2026-10-15 14:11 ` [PATCH vv2 1/1] " Stephan Rohr
2026-10-19 16:19   ` Tom Tromey
2026-10-21 13:47     ` Rohr, Stephan
2026-10-21 17:22       ` Tom Tromey

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=20261015141127.152846-1-stephan.rohr@intel.com \
    --to=stephan.rohr@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.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