From: Pierre Langlois <pierre.langlois@arm.com>
To: gdb-patches@sourceware.org
Cc: Pierre Langlois <pierre.langlois@arm.com>
Subject: [PATCH 0/2][GDBServer][AArch64] Enable support for Z0 packets
Date: Fri, 26 Jun 2015 13:42:00 -0000 [thread overview]
Message-ID: <1435326128-13705-1-git-send-email-pierre.langlois@arm.com> (raw)
Hi all,
This series of patches lets GDBServer handle software breakpoints for the
AArch64 target. The main reason for doing this is that it will allow us to
enable support for tracepoints later.
Simply enabling support for the Z0 packet uncovered an issue which is what the
first patch addresses: We need GDB and GDBServer using the same breakpoint
instruction. The second patch finally enables Z0 packets.
I ran the regression tests in a remote configuration on aarch64 which
activated the following previously unsupported test:
- PASS: gdb.base/dprintf.exp: 1st dprintf, agent
- PASS: gdb.base/dprintf.exp: 2nd dprintf, agent
- PASS: gdb.base/dprintf.exp: dprintf info 2
- PASS: gdb.mi/mi-dprintf.exp: mi expect stop
- PASS: gdb.mi/mi-dprintf.exp: mi 1st dprintf, agent
- PASS: gdb.mi/mi-dprintf.exp: mi info dprintf second time
- PASS: gdb.mi/mi-dprintf.exp: mi 2nd dprintf, agent
Thanks,
Pierre
Pierre Langlois (2):
[GDBServer][AArch64] Use the same break instruction as GDB
[GDBServer][AArch64] Enable support for Z0 packets
gdb/gdbserver/ChangeLog | 12 ++++++++++++
gdb/gdbserver/linux-aarch64-low.c | 16 +++++++++-------
2 files changed, 21 insertions(+), 7 deletions(-)
--
2.1.0
next reply other threads:[~2015-06-26 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 13:42 Pierre Langlois [this message]
2015-06-26 13:42 ` [PATCH 2/2] [GDBServer][AArch64] " Pierre Langlois
2015-06-29 8:08 ` Yao Qi
2015-06-26 13:42 ` [PATCH 1/2] [GDBServer][AArch64] Use the same break instruction as GDB Pierre Langlois
2015-06-29 8:07 ` Yao Qi
2015-06-29 9:40 ` [PATCH 0/2][GDBServer][AArch64] Enable support for Z0 packets Pierre Langlois
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=1435326128-13705-1-git-send-email-pierre.langlois@arm.com \
--to=pierre.langlois@arm.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).