Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Raunaq 12 <raunaq12@in.ibm.com>
Cc: Tom Tromey <tromey@redhat.com>,
	Ulrich Weigand <uweigand@de.ibm.com>,
		GDB Patches <gdb-patches@sourceware.org>,
	Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined.
Date: Sat, 10 Aug 2013 02:57:00 -0000	[thread overview]
Message-ID: <CAGWvnynu8QND=Q0xYqzvFmZFz2NA15WMbOPuG9OB25q-egpGew@mail.gmail.com> (raw)

[Trying again because GMail insists on sending HTML which
sourceware.org rejects.]

> When GDB is compiled in 64 BIT mode ptrace and ptracex calls are not
defined on AIX. So, instead we check if ptrace64 is defined, if it is then
we call that instead of ptrace/x.

Have you tested the patch in both 32 bit mode and 64 bit mode for both host
GDB and target debugee? I tried the earlier version of this patch from last
year and experienced problems debugging in 32 bit mode (I no longer could
debug GCC).

ptrace, ptracex and ptrace64 are defined in syscalls.exp

ptrace64                 syscall3264
# 32
ptrace                     syscall32
ptracex                   syscall32

As you wrote, ptrace and ptracex are 32 bit only APIs; ptrace64 is
available as 32 bit and 64 bit API.  ptrace64 is suppose to support 32 bit
debugee targets, but I experienced problems.

A configure probe of ptrace64 will compile and link in 32 bit mode and
configure will discover it as available when building 32 bit GDB.

Is your intention to always use ptrace64 when it is available or only to
use it for GDB built and hosted on 64 bit mode?

Thanks, David


             reply	other threads:[~2013-08-10  2:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-10  2:57 David Edelsohn [this message]
     [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
2013-08-22 23:32     ` Joel Brobecker
  -- 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='CAGWvnynu8QND=Q0xYqzvFmZFz2NA15WMbOPuG9OB25q-egpGew@mail.gmail.com' \
    --to=dje.gcc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=raunaq12@in.ibm.com \
    --cc=tromey@redhat.com \
    --cc=uweigand@de.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