This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.
- From: Joel Brobecker <brobecker at adacore dot com>
- To: David Edelsohn <dje dot gcc at gmail dot com>
- Cc: Raunaq 12 <raunaq12 at in dot ibm dot com>, GDB Patches <gdb-patches at sourceware dot org>, Mark Kettenis <mark dot kettenis at xs4all dot nl>, Ulrich Weigand <Ulrich dot Weigand at de dot ibm dot com>
- Date: Thu, 22 Aug 2013 16:32:34 -0700
- Subject: Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.
- References: <CAGWvnynVeLt6F-QREsP_CtQvwvtZgwqHxtcS6pn58LMf=AX=GA at mail dot gmail dot com> <OF91B6D42F dot B0CFCB9C-ON65257BC5 dot 004284AA-65257BC5 dot 0042F553 at in dot ibm dot com> <CAGWvnynzsNL--qPhHOhqZ912A4M9ZpXtT2JbjW4EHRodEXAF9Q at mail dot gmail dot com>
> I built gdb-7.6 with the ptrace64 patch (without --enable-64-bit-bfd)
> and it seems to work correctly on cc1plus. So at least the current
> patch does not harm debugging.
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
The error returned by ptrace64 is EIO (5), which means it thinks
the address is wrong (or else the request ID is invalid, but I doubt
that). I'm a bit rushed, as usual, but I still have a little extra
time today to dig a little further.
--
Joel