public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/6] Use PTRACE_GETREGSET and PTRACE_SETREGSET in arm-linux-nat.c
Date: Thu, 28 May 2015 14:20:00 -0000	[thread overview]
Message-ID: <1432822816-32327-1-git-send-email-yao.qi@linaro.org> (raw)

This patch series is to let GDB arm-linux-nat.c use ptrace commands
PTRACE_GETREGSET and PTRACE_SETREGSET if linux kernel supports.

Patch #1 and #2 are factoring out macros and variables into more
common files.  Patch #3 checks whether PTRACE_GETREGSET is supported by
linux kernel.  Patch #4 - #6 use PTRACE_{G,S}ETREGSET ptrace commands
to fetch and store general purpose registers, FP registers and VFP
registers.

The whole test series are tested on x86_64-linux and arm-linux (with
PTRACE_GETREGSET and without PTRACE_GETREGSET kernel support respectively).

After these patches, arm-linux-nat.c is similar to aarch64-linux-nat.c
in the aspect of fetching and storing registers.  It paves the way for
multi-arch support in aarch64 gdb (aarch64 gdb can do native debugging
for arm program), which is the motivation of this patch series.

*** BLURB HERE ***

Yao Qi (6):
  Move PTRACE_GETREGSET and PTRACE_SETREGSET to nat/linux-ptrace.h
  Move have_ptrace_getregset to linux-nat.c
  Check whether kernel supports PTRACE_GETREGSET
  Fetch and store GP registers by PTRACE_{G,S}ETREGSET
  Fetch and store FP registers by PTRACE_{G,S}ETREGSET
  Fetch and store VFP registers by PTRACE_{G,S}ETREGSET

 gdb/amd64-linux-nat.c          |   1 +
 gdb/arm-linux-nat.c            | 211 +++++++++++++++++++++++++++++++++++++----
 gdb/gdbserver/linux-s390-low.c |   8 --
 gdb/gdbserver/linux-x86-low.c  |   9 --
 gdb/i386-linux-nat.c           |   1 +
 gdb/linux-nat.c                |   3 +
 gdb/linux-nat.h                |   3 +
 gdb/nat/linux-ptrace.h         |   8 ++
 gdb/s390-linux-nat.c           |   9 +-
 gdb/x86-linux-nat.c            |   3 +-
 gdb/x86-linux-nat.h            |  10 --
 11 files changed, 212 insertions(+), 54 deletions(-)

-- 
1.9.1

             reply	other threads:[~2015-05-28 14:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 14:20 Yao Qi [this message]
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
2015-05-29 13:11     ` Yao Qi
2015-05-28 14:20 ` [PATCH 5/6] Fetch and store FP " Yao Qi
2015-05-28 14:20 ` [PATCH 3/6] Check whether kernel supports PTRACE_GETREGSET 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 6/6] Fetch and store VFP registers by PTRACE_{G,S}ETREGSET 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=1432822816-32327-1-git-send-email-yao.qi@linaro.org \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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).