From: Joel Brobecker <brobecker@adacore.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Raunaq 12 <raunaq12@in.ibm.com>,
GDB Patches <gdb-patches@sourceware.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: [RFA/ppc-aix] fix thread support breakage (was: "Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.")
Date: Fri, 23 Aug 2013 00:48:00 -0000 [thread overview]
Message-ID: <20130823004837.GC5221@adacore.com> (raw)
In-Reply-To: <20130822233234.GA13292@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hello again,
> Actually, I just found that it breaks thread support on 32bit AIX,
> at least. A simpler way to show the problem is:
>
> (gdb) x /x &__n_pthreads
> 0xf06a8258 <__n_pthreads>: Cannot access memory at address 0xf06a8258
>
> Prior to the patch, we have:
>
> (gdb) x /x &__n_pthreads
> 0xf06a8258 <__n_pthreads>: 0x00000003
Attached is the patch I checked in locally at AdaCore:
gdb/ChangeLog:
* rs6000-nat.c (rs6000_ptrace32): Cast "addr" to "uintptr_t"
instead of "long long" in call to ptrace64.
Tested on ppc-aix in full 32bit mode (both GDB and inferior are
32bit). I think the other scenario would be 64bit GDB debugging
a 32bit inferior, but I don't have a 64bit compiler to try it.
I'd like to commit this patch, unless there are comments/suggestions.
Thank you,
--
Joel
[-- Attachment #2: 0001-thread-support-broken-on-ppc-aix.patch --]
[-- Type: text/x-diff, Size: 2060 bytes --]
From 91f7d8c9ae626954479217739aaa476e79e5daeb Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Thu, 22 Aug 2013 20:33:27 -0400
Subject: [PATCH] thread support broken on ppc-aix.
Thread support got broken when adding 64bit support on ppc-aix.
Upon digging further, I found that the following patch...
| * gdb_ptrace.h: Use ptrace64 instead of ptrace if HAVE_PTRACE64
| is defined.
| * rs6000-nat.c: Check for __ld_info64_ if compiling 64 BIT gdb.
| (rs6000_ptrace32): Call ptrace64 instead of ptrace if present.
| (rs6000_ptrace64): Call ptace64 instead of ptracex if present.
| * configure.ac: Check for ptrace64.
| * configure, config.in: Regenerate.
... is responsible for this regression:
(gdb) x /x &__n_pthreads
0xf06a8258 <__n_pthreads>: Cannot access memory at address 0xf06a8258
Prior to the patch, we have:
(gdb) x /x &__n_pthreads
0xf06a8258 <__n_pthreads>: 0x00000003
The problem occurs inside rs6000_ptrace32, while calling ptrace64.
The address is given to rs6000_ptrace32 as an "int *", while
ptrace64 takes a "long long". The cast causes the address to be
sign-extended, which results in GDB trying to read the wrong address.
This patch fixes the issue by casting the address to a "uintptr_t"
instead, and letting the compiler do the implicit conversion to
"long long" in the function call.
gdb/ChangeLog:
* rs6000-nat.c (rs6000_ptrace32): Cast "addr" to "uintptr_t"
instead of "long long" in call to ptrace64.
---
gdb/rs6000-nat.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gdb/rs6000-nat.c b/gdb/rs6000-nat.c
index 0953356..b214cd9 100644
--- a/gdb/rs6000-nat.c
+++ b/gdb/rs6000-nat.c
@@ -132,7 +132,7 @@ static int
rs6000_ptrace32 (int req, int id, int *addr, int data, int *buf)
{
#ifdef HAVE_PTRACE64
- int ret = ptrace64 (req, id, (long long) addr, data, buf);
+ int ret = ptrace64 (req, id, (uintptr_t) addr, data, buf);
#else
int ret = ptrace (req, id, (int *)addr, data, buf);
#endif
--
1.7.0.4
next prev parent reply other threads:[~2013-08-23 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGWvnynVeLt6F-QREsP_CtQvwvtZgwqHxtcS6pn58LMf=AX=GA@mail.gmail.com>
2013-08-12 12:02 ` [PATCH 4/5] powerpc64-aix ptrace64 when defined Raunaq 12
2013-08-12 15:53 ` David Edelsohn
2013-08-12 12:11 ` Raunaq 12
2013-08-12 19:43 ` David Edelsohn
2013-08-22 23:32 ` Joel Brobecker
2013-08-23 0:48 ` Joel Brobecker [this message]
2013-08-23 7:23 ` [RFA/ppc-aix] fix thread support breakage (was: "Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.") David Edelsohn
2013-08-23 13:34 ` Joel Brobecker
[not found] ` <CAGWvnyna5R2AR0imAC4W+aCJXPFjwPm+45yP9VOgkO68T7sF7w@mail.gmail.com>
[not found] ` <OFC7611E7B.F19F366D-ON65257BE2.003745A0-65257BE2.00386093@in.ibm.com>
2013-09-17 18:38 ` [RFA/ppc-aix] fix thread support breakage Tom Tromey
2013-08-29 21:03 ` Checked in: [RFA/ppc-aix] fix thread support breakage (was: "Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.") 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=20130823004837.GC5221@adacore.com \
--to=brobecker@adacore.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=raunaq12@in.ibm.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