From: Eduard Sargsyan <eduard.sargsyan@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/1] Crash on register invalidation
Date: Tue, 19 Dec 2023 15:14:47 +0000 [thread overview]
Message-ID: <20231219151448.23519-1-eduard.sargsyan@intel.com> (raw)
From: "Sargsyan, Eduard" <eduard.sargsyan@intel.com>
Hi all,
There was an assertion triggered, when gdb tries to invalidate register
cache after gdbserver connection is not dead. I beleive in such cases we
do not need asssertion.
Regards,
Eduard
Eduard Sargsyan (1):
gdb: fix assert after register write failure
gdb/regcache.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
--
2.34.1
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2023-12-19 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 15:14 Eduard Sargsyan [this message]
2023-12-19 15:14 ` [PATCH 1/1] gdb: fix assert after register write failure Eduard Sargsyan
2023-12-22 16:10 ` Tom Tromey
2023-12-22 16:36 ` Simon Marchi
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=20231219151448.23519-1-eduard.sargsyan@intel.com \
--to=eduard.sargsyan@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).