Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Marcus Shawcroft <marcus.shawcroft@arm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdbserver ptrace() argument type cleanups.
Date: Mon, 04 Feb 2013 17:35:00 -0000	[thread overview]
Message-ID: <510FF165.4090906@redhat.com> (raw)
In-Reply-To: <510FF048.8070701@arm.com>

Hi Marcus,

On 02/04/2013 05:30 PM, Marcus Shawcroft wrote:

> This patch is ripped out of the aarch64 gdbserver patch here:
> 
> http://sourceware.org/ml/gdb-patches/2013-01/msg00535.html
> 
> These changes are not directly related to the aarch64 port itself. Since ptrace() has a variadic prototype, the anonymous arguments, notably arguments 3 and 4, should be given their correct types.

Excellent.  Thanks for doing this.

>    gdb/gdbserver/
> 
>         * linux-low.c (handle_extended_wait, linux_create_inferior)
>         (linux_attach_lwp_1, linux_kill_one_lwp, linux_attach_one_lwp)
>         (dequeue_one_deferred_signal, linux_resume_one_thread)
>         (fetch_register, linux_write_memory, linux_enable_event_reporting)
>         (linux_tracefork_grandchild, linux_test_for_tracefork)
>         (linux_read_offsets, linux_xfer_siginfo, linux_xfer_siginfo ): Add

Spurious space ------------------------------------------------------^

>         PTRACE_ARG3_TYPE and PTRACE_ARG4_TYPE cast to ptrace arguments
>         where the argument is 0.

This is OK.

Thanks!

-- 
Pedro Alves


  reply	other threads:[~2013-02-04 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 17:31 Marcus Shawcroft
2013-02-04 17:35 ` Pedro Alves [this message]
2013-02-04 17:41   ` Marcus Shawcroft
2013-02-04 18:57 ` Mark Kettenis
2013-02-04 19:01   ` Tom Tromey
2013-02-04 19:25     ` Pedro Alves
2013-02-04 22:09     ` Mark Kettenis
2013-02-04 19:04   ` Marcus Shawcroft

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=510FF165.4090906@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marcus.shawcroft@arm.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