Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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>, Tom Tromey <tom@tromey.com>,
	Francois Bedard <fbedard@synopsys.com>
Subject: [PUSHED] arc: Write correct "eret" value during register collection
Date: Thu, 12 Nov 2020 17:05:20 +0100	[thread overview]
Message-ID: <20201112160520.20364-1-shahab.vahedi@gmail.com> (raw)
In-Reply-To: <20201112134310.8544-1-shahab.vahedi@gmail.com>

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.

v2:
- Fix a copy/paste issue as rightfully addressed by Tom [1].

[1]
https://sourceware.org/pipermail/gdb-patches/2020-November/173208.html

gdb/ChangeLog:

	* arc-linux-tdep.c (collect_register): Populate "eret" by
	"pc" value from the regcache when asked for "pc" value.
---
 gdb/ChangeLog        |  5 +++++
 gdb/arc-linux-tdep.c | 10 +++++++---
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 038d45f4ec4..4d1f5241e8c 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2020-11-12  Shahab Vahedi  <shahab@synopsys.com>
+
+	* arc-linux-tdep.c (collect_register): Populate "eret" by
+	"pc" value from the regcache when asked for "pc" value.
+
 2020-11-12  Tom Tromey  <tom@tromey.com>
 
 	PR rust/26799:
diff --git a/gdb/arc-linux-tdep.c b/gdb/arc-linux-tdep.c
index 9ff5f1214a1..6e74bae8056 100644
--- a/gdb/arc-linux-tdep.c
+++ b/gdb/arc-linux-tdep.c
@@ -319,8 +319,10 @@ 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;
 
   /* The address where the execution has stopped is in pseudo-register
@@ -332,8 +334,10 @@ 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];
+  else
+    offset = arc_linux_core_reg_offsets[regnum];
+  regcache->raw_collect (regnum, buf + offset);
 }
 
 void
-- 
2.29.2


  parent reply	other threads:[~2020-11-12 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 13:43 [PATCH] " Shahab Vahedi via Gdb-patches
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 ` Shahab Vahedi via Gdb-patches [this message]
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=20201112160520.20364-1-shahab.vahedi@gmail.com \
    --to=gdb-patches@sourceware.org \
    --cc=fbedard@synopsys.com \
    --cc=shahab.vahedi@gmail.com \
    --cc=shahab@synopsys.com \
    --cc=tom@tromey.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