From: Doug Evans <dje@google.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 4/6] Fetch and store GP registers by PTRACE_{G,S}ETREGSET
Date: Thu, 28 May 2015 18:50:00 -0000 [thread overview]
Message-ID: <CADPb22SBdBkrNPAg9s1RU0gF3Ob73v7XYdL-jDUNMRTm6OP5-w@mail.gmail.com> (raw)
In-Reply-To: <1432822816-32327-5-git-send-email-yao.qi@linaro.org>
On Thu, May 28, 2015 at 7:20 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
> If kernel supports PTRACE_GETREGSET, GDB uses PTRACE_{G,S}ETREGSET
> to fetch and store GP registers.
>
> gdb:
>
> 2015-05-28 Yao Qi <yao.qi@linaro.org>
>
> * arm-linux-nat.c (fetch_register): Use PTRACE_GETREGSET.
> (fetch_regs): Likewise.
> (store_regs): Use PTRACE_SETREGSET.
> (store_register): Likewise.
> ---
> gdb/arm-linux-nat.c | 79 ++++++++++++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 72 insertions(+), 7 deletions(-)
>
> diff --git a/gdb/arm-linux-nat.c b/gdb/arm-linux-nat.c
> index 877559e..0a86ed6 100644
> --- a/gdb/arm-linux-nat.c
> +++ b/gdb/arm-linux-nat.c
> @@ -225,7 +225,18 @@ fetch_register (struct regcache *regcache, int regno)
> /* Get the thread id for the ptrace call. */
> tid = GET_THREAD_ID (inferior_ptid);
>
> - ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> + if (have_ptrace_getregset == 1)
Hi.
The == 1 in this test hinders readability (to me anyway).
[It occurs here and in 5/6, 6/6.]
The name suggests the variable is a boolean, so I'm
left wondering "Can it have values other than 0/1,
and is the else clause correct for those other values?"
Digging deeper the reader would find the variable is tri-state,
but the initial -1 value should never be seen here (at least
that's the intuitive choice).
If one wanted to add an assert that the value is not -1 here
that'd be ok, though one could also argue it's overkill.
I don't have a preference either way.
But I suggest removing the "== 1" in the test.
> + {
> + struct iovec iov;
> +
> + iov.iov_base = ®s;
> + iov.iov_len = sizeof (regs);
> +
> + ret = ptrace (PTRACE_GETREGSET, tid, NT_PRSTATUS, &iov);
> + }
> + else
> + ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> +
> if (ret < 0)
> {
> warning (_("Unable to fetch general register."));
> @@ -266,8 +277,19 @@ fetch_regs (struct regcache *regcache)
>
> /* Get the thread id for the ptrace call. */
> tid = GET_THREAD_ID (inferior_ptid);
> -
> - ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> +
> + if (have_ptrace_getregset == 1)
> + {
> + struct iovec iov;
> +
> + iov.iov_base = ®s;
> + iov.iov_len = sizeof (regs);
> +
> + ret = ptrace (PTRACE_GETREGSET, tid, NT_PRSTATUS, &iov);
> + }
> + else
> + ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> +
> if (ret < 0)
> {
> warning (_("Unable to fetch general registers."));
> @@ -306,7 +328,18 @@ store_register (const struct regcache *regcache, int regno)
> tid = GET_THREAD_ID (inferior_ptid);
>
> /* Get the general registers from the process. */
> - ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> + if (have_ptrace_getregset == 1)
> + {
> + struct iovec iov;
> +
> + iov.iov_base = ®s;
> + iov.iov_len = sizeof (regs);
> +
> + ret = ptrace (PTRACE_GETREGSET, tid, NT_PRSTATUS, &iov);
> + }
> + else
> + ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> +
> if (ret < 0)
> {
> warning (_("Unable to fetch general registers."));
> @@ -322,7 +355,18 @@ store_register (const struct regcache *regcache, int regno)
> regcache_raw_collect (regcache, ARM_PC_REGNUM,
> (char *) ®s[ARM_PC_REGNUM]);
>
> - ret = ptrace (PTRACE_SETREGS, tid, 0, ®s);
> + if (have_ptrace_getregset == 1)
> + {
> + struct iovec iov;
> +
> + iov.iov_base = ®s;
> + iov.iov_len = sizeof (regs);
> +
> + ret = ptrace (PTRACE_SETREGSET, tid, NT_PRSTATUS, &iov);
> + }
> + else
> + ret = ptrace (PTRACE_SETREGS, tid, 0, ®s);
> +
> if (ret < 0)
> {
> warning (_("Unable to store general register."));
> @@ -340,7 +384,18 @@ store_regs (const struct regcache *regcache)
> tid = GET_THREAD_ID (inferior_ptid);
>
> /* Fetch the general registers. */
> - ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> + if (have_ptrace_getregset == 1)
> + {
> + struct iovec iov;
> +
> + iov.iov_base = ®s;
> + iov.iov_len = sizeof (regs);
> +
> + ret = ptrace (PTRACE_GETREGSET, tid, NT_PRSTATUS, &iov);
> + }
> + else
> + ret = ptrace (PTRACE_GETREGS, tid, 0, ®s);
> +
> if (ret < 0)
> {
> warning (_("Unable to fetch general registers."));
> @@ -357,7 +412,17 @@ store_regs (const struct regcache *regcache)
> regcache_raw_collect (regcache, ARM_PS_REGNUM,
> (char *) ®s[ARM_CPSR_GREGNUM]);
>
> - ret = ptrace (PTRACE_SETREGS, tid, 0, ®s);
> + if (have_ptrace_getregset == 1)
> + {
> + struct iovec iov;
> +
> + iov.iov_base = ®s;
> + iov.iov_len = sizeof (regs);
> +
> + ret = ptrace (PTRACE_SETREGSET, tid, NT_PRSTATUS, &iov);
> + }
> + else
> + ret = ptrace (PTRACE_SETREGS, tid, 0, ®s);
>
> if (ret < 0)
> {
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-05-28 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 14:20 [PATCH 0/6] Use PTRACE_GETREGSET and PTRACE_SETREGSET in arm-linux-nat.c Yao Qi
2015-05-28 14:20 ` [PATCH 3/6] Check whether kernel supports PTRACE_GETREGSET Yao Qi
2015-05-28 14:20 ` [PATCH 6/6] Fetch and store VFP registers by PTRACE_{G,S}ETREGSET Yao Qi
2015-05-28 14:20 ` [PATCH 5/6] Fetch and store FP " Yao Qi
2015-05-28 14:20 ` [PATCH 2/6] Move have_ptrace_getregset to linux-nat.c Yao Qi
2015-05-28 14:20 ` [PATCH 1/6] Move PTRACE_GETREGSET and PTRACE_SETREGSET to nat/linux-ptrace.h Yao Qi
2015-05-28 14:20 ` [PATCH 4/6] Fetch and store GP registers by PTRACE_{G,S}ETREGSET Yao Qi
2015-05-28 18:50 ` Doug Evans [this message]
2015-05-29 13:11 ` Yao Qi
2015-05-29 8:10 ` [PATCH 0/6] Use PTRACE_GETREGSET and PTRACE_SETREGSET in arm-linux-nat.c Gary Benson
2015-06-01 11:17 ` Yao Qi
2015-06-02 7:57 ` Mark Wielaard
2015-06-02 9:30 ` Yao Qi
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=CADPb22SBdBkrNPAg9s1RU0gF3Ob73v7XYdL-jDUNMRTm6OP5-w@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@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