public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Luis Machado <luis.machado@arm.com>,
	John Baldwin <jhb@freebsd.org>,
	Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/2] Fix gdb.arch/aarch64-sme-core-*.exp failures
Date: Thu, 30 Nov 2023 16:20:45 -0500	[thread overview]
Message-ID: <20231130212057.722990-1-simon.marchi@efficios.com> (raw)

While testing my pseudo-register series on QEMU AArch64 (to test SVE and
SME support), I noticed some pre-existing failures in the
gdb.arch/aarch64-sme-core-*.exp.  This small series fixes them.

Simon Marchi (2):
  gdb: return when exceeding buffer size in regcache::transfer_regset
  gdb: add missing regcache_map_entry array null terminators in
    aarch64-linux-tdep.c

 gdb/aarch64-linux-tdep.c | 7 +++++--
 gdb/regcache.c           | 2 +-
 2 files changed, 6 insertions(+), 3 deletions(-)


base-commit: d5835df2eebf8e9cd3ae35b683c831c2a16a5269
-- 
2.43.0


             reply	other threads:[~2023-11-30 21:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 21:20 Simon Marchi [this message]
2023-11-30 21:20 ` [PATCH 1/2] gdb: return when exceeding buffer size in regcache::transfer_regset Simon Marchi
2023-11-30 23:42   ` John Baldwin
2023-12-01  0:02     ` Simon Marchi
2023-12-01  9:13   ` Luis Machado
2023-11-30 21:20 ` [PATCH 2/2] gdb: add missing regcache_map_entry array null terminators in aarch64-linux-tdep.c Simon Marchi
2023-11-30 23:44   ` John Baldwin
2023-12-01  0:03     ` Simon Marchi
2023-12-01  9:12   ` Luis Machado
2023-12-01 16:21     ` Simon Marchi

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=20231130212057.722990-1-simon.marchi@efficios.com \
    --to=simon.marchi@efficios.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.org \
    --cc=luis.machado@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).