From: David Edelsohn <dje.gcc@gmail.com>
To: Raunaq 12 <raunaq12@in.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.
Date: Mon, 12 Aug 2013 19:43:00 -0000 [thread overview]
Message-ID: <CAGWvnynzsNL--qPhHOhqZ912A4M9ZpXtT2JbjW4EHRodEXAF9Q@mail.gmail.com> (raw)
In-Reply-To: <OF91B6D42F.B0CFCB9C-ON65257BC5.004284AA-65257BC5.0042F553@in.ibm.com>
On Mon, Aug 12, 2013 at 8:10 AM, Raunaq 12 <raunaq12@in.ibm.com> wrote:
> My initial intention was to use ptrace64 only if ptrace64 was available and
> GDB was built in 64 BIT. But after a few discussions over this, I decided
> to use ptrace64 when ever the API is defined.
>
> So, this present patch would use
> ptrace64 even for a 32 bit build as you rightly noticed.
> This did not change the test results for a 32 bit build of GDB.
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.
Thanks, David
next prev parent reply other threads:[~2013-08-12 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGWvnynVeLt6F-QREsP_CtQvwvtZgwqHxtcS6pn58LMf=AX=GA@mail.gmail.com>
2013-08-12 12:02 ` Raunaq 12
2013-08-12 15:53 ` David Edelsohn
2013-08-12 12:11 ` Raunaq 12
2013-08-12 19:43 ` David Edelsohn [this message]
2013-08-22 23:32 ` Joel Brobecker
2013-08-23 0:48 ` [RFA/ppc-aix] fix thread support breakage (was: "Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.") Joel Brobecker
2013-08-23 7:23 ` David Edelsohn
2013-08-23 13:34 ` Joel Brobecker
2013-08-23 15:14 ` David Edelsohn
2013-09-10 10:16 ` Raunaq 12
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
2013-08-10 2:57 [PATCH 4/5] powerpc64-aix ptrace64 when defined David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2013-08-01 11:28 Raunaq 12
2013-08-01 13:26 ` Mark Kettenis
2013-08-02 6:56 ` Raunaq 12
[not found] ` <OF21D042FF.CF4E8435-ON65257BBB.0024F10A-65257BBB.00261FEF@LocalDomain>
2013-08-07 11:39 ` Raunaq 12
2013-08-07 13:36 ` Raunaq 12
2013-08-07 14:44 ` Ulrich Weigand
2013-07-29 6:17 Raunaq 12
2013-07-24 13:01 Raunaq 12
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=CAGWvnynzsNL--qPhHOhqZ912A4M9ZpXtT2JbjW4EHRodEXAF9Q@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=Ulrich.Weigand@de.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).