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/4 V6] Process record and reverse debugging support on aarch64-linux
Date: Tue, 19 May 2015 13:22:00 -0000	[thread overview]
Message-ID: <1432041752-4638-1-git-send-email-yao.qi@linaro.org> (raw)

This patch series is about adding process recording and reverse
debugging for aarch64-linux target.

This is V6, with some changes on top of V5
https://sourceware.org/ml/gdb-patches/2015-05/msg00239.html
with some changes,

 - Indent the code, and fix some format issues,
 - Fix one bug about handling SIMD instructions,
 - Always record register CPSR [1]
 - Pick up a small set of instructions from Omair's test in the my
   test case,
 - Complete changelog and commit log message.

There are 7 fails in gdb.reverse, shown in the commit log of patch
#3, which are not related to instruction decoding and recording for
aarch64.

[1] aarch64 doesn't have CPSR register, which only exist on ARM or
aarch32 state.  In aarch64, linux kernel ptrace interface exposes
64-bit PSTATE rather than CPSR register.  PSTATE may be changed
during the execution of instructions, for example, after
single step.  In process record, we have to always record CPSR.
I plan to replace CPSR with PSTATE in aarch64 separately.

*** BLURB HERE ***

Omair Javaid (3):
  NEWS entry about aarch64-linux record/replay support
  Implements aarch64 process record and reverse debugging support
  Enables gdb.reverse testsuite for aarch64*-linux targets

Yao Qi (1):
  New gdb.reverse test case for aarch64 instructions

 gdb/NEWS                              |   4 +
 gdb/aarch64-linux-tdep.c              | 739 ++++++++++++++++++++++++++
 gdb/aarch64-tdep.c                    | 967 ++++++++++++++++++++++++++++++++++
 gdb/aarch64-tdep.h                    |   6 +
 gdb/configure.tgt                     |   2 +-
 gdb/linux-record.h                    |   1 +
 gdb/testsuite/gdb.reverse/aarch64.c   |  99 ++++
 gdb/testsuite/gdb.reverse/aarch64.exp | 115 ++++
 gdb/testsuite/lib/gdb.exp             |   2 +
 9 files changed, 1934 insertions(+), 1 deletion(-)
 create mode 100644 gdb/testsuite/gdb.reverse/aarch64.c
 create mode 100644 gdb/testsuite/gdb.reverse/aarch64.exp

-- 
1.9.1

             reply	other threads:[~2015-05-19 13:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 13:22 Yao Qi [this message]
2015-05-19 13:22 ` [PATCH 1/4] NEWS entry about aarch64-linux record/replay support Yao Qi
2015-05-19 13:22 ` [PATCH 2/4] Implements aarch64 process record and reverse debugging support Yao Qi
2015-05-21 20:23   ` Pedro Alves
2015-05-26 11:41     ` Yao Qi
2015-05-26 20:00       ` Edjunior Barbosa Machado
2015-05-27  8:21         ` Yao Qi
2015-05-27  9:23           ` Yao Qi
2015-05-27 10:22           ` Yao Qi
2015-05-27 14:12             ` Edjunior Barbosa Machado
2015-05-27 15:05               ` Yao Qi
2015-05-27 15:54                 ` Edjunior Barbosa Machado
2015-05-27 16:18                   ` Yao Qi
2015-05-19 13:23 ` [PATCH 3/4] Enables gdb.reverse testsuite for aarch64*-linux targets Yao Qi
2015-05-19 13:23 ` [PATCH 4/4] New gdb.reverse test case for aarch64 instructions Yao Qi
2015-05-21 20:22   ` Pedro Alves
2015-05-26 11:26     ` 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=1432041752-4638-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).