From: Thiago Jung Bauermann via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Fix bug in aarch64-linux GDB when inferior changes SVE vector length
Date: Thu, 28 Jul 2022 01:23:04 +0000 [thread overview]
Message-ID: <20220728012306.157639-1-thiago.bauermann@linaro.org> (raw)
Hello,
While working on gdbserver support for the case where the inferior changes
the SVE vector length, I noticed aproblem in the same scenario when doing
native debugging (details are in patch 1).
The testcase fails without the fix, and passes with it. Regression tested on
aarch64-linux native on Ubuntu 20.04.
Thanks,
Thiago
Thiago Jung Bauermann (2):
gdb/aarch64: Fix thread's gdbarch when SVE vector length changes
gdb/testsuite: Add test for AArch64 Scalable Vector Extension
gdb/aarch64-linux-nat.c | 11 +++-
gdb/aarch64-tdep.c | 25 ++++++++
gdb/aarch64-tdep.h | 2 +
gdb/testsuite/gdb.arch/aarch64-sve.c | 61 +++++++++++++++++++
gdb/testsuite/gdb.arch/aarch64-sve.exp | 81 ++++++++++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 4 ++
gdb/testsuite/lib/mi-support.exp | 4 --
7 files changed, 181 insertions(+), 7 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/aarch64-sve.c
create mode 100644 gdb/testsuite/gdb.arch/aarch64-sve.exp
next reply other threads:[~2022-07-28 1:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 1:23 Thiago Jung Bauermann via Gdb-patches [this message]
2022-07-28 1:23 ` [PATCH 1/2] gdb/aarch64: Fix thread's gdbarch when SVE vector length changes Thiago Jung Bauermann via Gdb-patches
2022-07-28 13:03 ` Luis Machado via Gdb-patches
2022-08-02 4:15 ` Thiago Jung Bauermann via Gdb-patches
2022-07-28 1:23 ` [PATCH 2/2] gdb/testsuite: Add test for AArch64 Scalable Vector Extension Thiago Jung Bauermann via Gdb-patches
2022-07-28 13:03 ` Luis Machado via Gdb-patches
2022-08-02 22:59 ` Thiago Jung Bauermann via Gdb-patches
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=20220728012306.157639-1-thiago.bauermann@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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