Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] IA64: EC, the Epilog Count register, is available in ptrace.
Date: Wed, 28 Mar 2012 14:55:00 -0000	[thread overview]
Message-ID: <20120328145451.12183.7502.stgit@brno.lan> (raw)
In-Reply-To: <4F730961.6030003@redhat.com>

> gcore.exp failures related to these issues.  It shows the $f0/$f1 issue, and
> also, that $ec is read back from the core as 0, but it is read as
> *unavailable* when debugging a live process.  The latter is because
> have (ia64-linux-nat.c):
>
> static int u_offsets[] =
>   {
> ...
>     PT_AR_LC,
>     -1,		/* Not available: EC, the Epilog Count register.  */
>
> But in ia64-linux-nat.c:supply_gregset:
>
>   regcache_raw_supply (regcache, IA64_LC_REGNUM, regp + 53);
>   regcache_raw_supply (regcache, IA64_EC_REGNUM, regp + 54);
>
> which is suspicious (the registers is not retrievable with ptrace, but
> it's in the core?).  Indeed, on this system's /usr/include/asm/ptrace_offsets.h
> I see:
>
> #define PT_AR_EC                0x0800
> #define PT_AR_LC                0x0808
>
> So it does look like it is available with ptrace.

Git blame on the kernel's sources shows the define always existed for
at least as long as there's git history (1da177e, 2.6.12-rc2).  I
haven't checked further back...

WDYT?

2012-03-28  Pedro Alves  <palves@redhat.com>

	* ia64-linux-nat.c (u_offsets): Map IA64_EC_REGNUM to PT_AR_EC.
---
 gdb/ia64-linux-nat.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/gdb/ia64-linux-nat.c b/gdb/ia64-linux-nat.c
index 60b873b..24bde2d 100644
--- a/gdb/ia64-linux-nat.c
+++ b/gdb/ia64-linux-nat.c
@@ -272,7 +272,7 @@ static int u_offsets[] =
     -1, -1, -1, -1, -1, -1, -1, -1, -1,
     PT_AR_PFS,
     PT_AR_LC,
-    -1,		/* Not available: EC, the Epilog Count register.  */
+    PT_AR_EC,
     -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
     -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
     -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,


  reply	other threads:[~2012-03-28 14:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 16:55 [RFA/commit/ia64-linux] Allow libunwind to fetch register 0 Joel Brobecker
2011-10-25 17:27 ` Pedro Alves
2011-10-25 17:37   ` Pedro Alves
2011-10-25 20:49   ` Joel Brobecker
2011-10-26  0:27     ` Pedro Alves
2012-03-27 19:32     ` Pedro Alves
2012-03-27 23:03       ` Joel Brobecker
2012-03-28 12:52         ` Pedro Alves
2012-03-28 14:55           ` Pedro Alves [this message]
2012-03-28 17:12             ` [PATCH] IA64: EC, the Epilog Count register, is available in ptrace Joel Brobecker
2012-03-28 17:55               ` Pedro Alves
2012-03-28 14:55           ` [PATCH] IA64: $fr0==0.0, $fr1==1.0 Pedro Alves
2012-03-28 17:15             ` Joel Brobecker
2012-03-28 17:56               ` Pedro Alves
2012-03-28 17:10           ` [RFA/commit/ia64-linux] Allow libunwind to fetch register 0 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=20120328145451.12183.7502.stgit@brno.lan \
    --to=palves@redhat.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