From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [FYI] Use pulongest in aarch64-linux-tdep.c
Date: Wed, 03 Oct 2018 01:31:00 -0000 [thread overview]
Message-ID: <20181003013112.15618-1-tom@tromey.com> (raw)
I tried a build on macOS today and it failed due to a mismatch between
the printf format and the type in aarch64-linux-tdep.c. This patch
fixes the problem by using pulongest and %s rather than %ld.
gdb/ChangeLog
2018-10-02 Tom Tromey <tom@tromey.com>
* aarch64-linux-tdep.c (aarch64_linux_sigframe_init): Use pulongest.
---
gdb/ChangeLog | 4 ++++
gdb/aarch64-linux-tdep.c | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index e55b1a726f..f2962075c5 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -247,8 +247,8 @@ aarch64_linux_sigframe_init (const struct tramp_frame *self,
vq = sve_vq_from_vl (extract_unsigned_integer (buf, 2, byte_order));
if (vq != tdep->vq)
- error (_("Invalid vector length in signal frame %d vs %ld."), vq,
- tdep->vq);
+ error (_("Invalid vector length in signal frame %d vs %s."), vq,
+ pulongest (tdep->vq));
if (size >= AARCH64_SVE_CONTEXT_SIZE (vq))
sve_regs = section + AARCH64_SVE_CONTEXT_REGS_OFFSET;
--
2.17.1
next reply other threads:[~2018-10-03 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 1:31 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-15 16:08 Tom Tromey
2018-09-06 4:17 ` Sergio Durigan Junior
2018-09-06 4:43 ` Tom Tromey
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=20181003013112.15618-1-tom@tromey.com \
--to=tom@tromey.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