From: Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Shahab Vahedi <shahab.vahedi@gmail.com>,
Shahab Vahedi <shahab@synopsys.com>,
Francois Bedard <fbedard@synopsys.com>
Subject: [PATCH] arc: Write correct "eret" value during register collection
Date: Thu, 12 Nov 2020 14:43:10 +0100 [thread overview]
Message-ID: <20201112134310.8544-1-shahab.vahedi@gmail.com> (raw)
From: Shahab Vahedi <shahab@synopsys.com>
In collect_register() function of arc-linux-tdep.c, the "eret"
(exception return) register value was not being reported correctly.
This patch fixes that.
Background:
When asked for the "pc" value, we have to update the "eret" register
with GDB's STOP_PC. The "eret" instructs the kernel code where to
jump back when an instruction has stopped due to a breakpoint. This
is how collect_register() was doing so:
--------------8<--------------
if (regnum == gdbarch_pc_regnum (gdbarch))
regnum = ARC_ERET_REGNUM;
regcache->raw_collect (regnum, buf + arc_linux_core_reg_offsets[regnum]);
-------------->8--------------
Root cause:
Although this is using the correct offset (ERET register's), it is also
changing the REGNUM itself. Therefore, raw_collect (regnum, ...) is
not reading from "pc" anymore.
gdb/ChangeLog:
* arc-linux-tdep.c (collect_register): Use "eret" value while
still writing to "pc" register cache.
---
gdb/arc-linux-tdep.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/gdb/arc-linux-tdep.c b/gdb/arc-linux-tdep.c
index 9ff5f1214a1..3530c7cbdd8 100644
--- a/gdb/arc-linux-tdep.c
+++ b/gdb/arc-linux-tdep.c
@@ -319,9 +319,13 @@ static void
collect_register (const struct regcache *regcache, struct gdbarch *gdbarch,
int regnum, gdb_byte *buf)
{
+ int offset;
+
/* Skip non-existing registers. */
- if ((arc_linux_core_reg_offsets[regnum] == ARC_OFFSET_NO_REGISTER))
+ if (arc_linux_core_reg_offsets[regnum] == ARC_OFFSET_NO_REGISTER)
return;
+ else
+ offset = arc_linux_core_reg_offsets[ARC_ERET_REGNUM];
/* The address where the execution has stopped is in pseudo-register
STOP_PC. However, when kernel code is returning from the exception,
@@ -332,8 +336,8 @@ collect_register (const struct regcache *regcache, struct gdbarch *gdbarch,
the program will continue at the address after the current instruction.
*/
if (regnum == gdbarch_pc_regnum (gdbarch))
- regnum = ARC_ERET_REGNUM;
- regcache->raw_collect (regnum, buf + arc_linux_core_reg_offsets[regnum]);
+ offset = arc_linux_core_reg_offsets[ARC_ERET_REGNUM];
+ regcache->raw_collect (regnum, buf + offset);
}
void
--
2.29.2
next reply other threads:[~2020-11-12 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 13:43 Shahab Vahedi via Gdb-patches [this message]
2020-11-12 14:36 ` Tom Tromey
2020-11-12 15:46 ` Shahab Vahedi via Gdb-patches
2020-11-12 15:42 ` [PATCH v2] " Shahab Vahedi via Gdb-patches
2020-11-12 15:43 ` Tom Tromey
2020-11-12 16:05 ` [PUSHED] " Shahab Vahedi via Gdb-patches
2020-12-04 10:57 ` [PUSHED gdb-10-branch] " Shahab Vahedi via Gdb-patches
2020-12-04 14:10 ` Joel Brobecker
2020-12-04 14:44 ` Shahab Vahedi via Gdb-patches
2020-12-04 14:53 ` Joel Brobecker
2020-12-04 15:38 ` Shahab Vahedi via Gdb-patches
2020-12-05 8:12 ` Joel Brobecker
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=20201112134310.8544-1-shahab.vahedi@gmail.com \
--to=gdb-patches@sourceware.org \
--cc=fbedard@synopsys.com \
--cc=shahab.vahedi@gmail.com \
--cc=shahab@synopsys.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