From: Luis Machado <luis.machado@linaro.org>
To: gdb-patches@sourceware.org
Cc: alan.hayward@arm.com, tankut.baris.aktemur@intel.com
Subject: [PATCH 0/2,v2][AArch64]Handle additional brk instruction patterns
Date: Mon, 13 Jan 2020 17:25:00 -0000 [thread overview]
Message-ID: <20200113172524.7201-1-luis.machado@linaro.org> (raw)
This patch teaches GDB how to handle additional breakpoint instruction
patterns for aarch64.
Luis Machado (2):
[AArch64] Recognize more program breakpoint patterns
[AArch64] Test handling of additional brk instruction patterns
gdb/aarch64-tdep.c | 39 +++++++++++
gdb/arch-utils.c | 37 ++++++++++
gdb/arch-utils.h | 4 ++
gdb/breakpoint.c | 46 ++-----------
gdb/breakpoint.h | 5 --
gdb/gdbarch.c | 23 +++++++
gdb/gdbarch.h | 7 ++
gdb/gdbarch.sh | 4 ++
gdb/infrun.c | 4 +-
gdb/testsuite/gdb.arch/aarch64-brk-patterns.c | 30 +++++++++
.../gdb.arch/aarch64-brk-patterns.exp | 67 +++++++++++++++++++
11 files changed, 220 insertions(+), 46 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/aarch64-brk-patterns.c
create mode 100644 gdb/testsuite/gdb.arch/aarch64-brk-patterns.exp
--
2.17.1
next reply other threads:[~2020-01-13 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 17:25 Luis Machado [this message]
2020-01-13 17:25 ` [PATCH 1/2][AArch64] Recognize more program breakpoint patterns Luis Machado
2020-01-13 17:30 ` [PATCH 2/2][AArch64] Test handling of additional brk instruction patterns Luis Machado
2020-01-14 5:03 ` Simon Marchi
2020-01-14 13:45 ` Luis Machado
2020-01-14 15:37 ` Simon Marchi
[not found] ` <BYAPR11MB3030A0EBC8F50F7B7B0F2081C4340@BYAPR11MB3030.namprd11.prod.outlook.com>
2020-01-14 13:59 ` Luis Machado
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=20200113172524.7201-1-luis.machado@linaro.org \
--to=luis.machado@linaro.org \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.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