Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: PATCH: PR gdb/13969: GDBserver doesn't check unsupported binary
Date: Thu, 12 Apr 2012 17:20:00 -0000	[thread overview]
Message-ID: <4F870888.9020803@redhat.com> (raw)
In-Reply-To: <CAMe9rOpeuuzu-3ZHien3XCfXVi2pcXeLC-6Ap8jbXUk+hA2Dhw@mail.gmail.com>

On 04/12/2012 05:45 PM, H.J. Lu wrote:

> x32 ptrace returns x32 siginfo, 


ok.

> which is compatible with ia32 inferior


I believe clock_t will be 64-bit with x32, however, right?
If so, amd64-linux-nat.c:compat_siginfo_from_siginfo|siginfo_from_compat_siginfo
(and the gdbserver equivalents) will need adjustment (for the 64-bit X x32 case).
This is something most probably not caught by the testsuite.

-- 
Pedro Alves


  reply	other threads:[~2012-04-12 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 20:36 H.J. Lu
2012-04-12 13:52 ` Pedro Alves
2012-04-12 15:58   ` H.J. Lu
2012-04-12 16:01     ` Pedro Alves
2012-04-12 16:38       ` H.J. Lu
2012-04-12 16:45         ` Pedro Alves
2012-04-12 16:53           ` H.J. Lu
2012-04-12 17:20             ` Pedro Alves [this message]
2012-04-12 18:05               ` H.J. Lu

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=4F870888.9020803@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.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