From: Tom Tromey <tom@tromey.com>
To: Mark Wielaard <mark@klomp.org>
Cc: gdb-patches@sourceware.org, Keith Seitz <keiths@redhat.com>
Subject: Re: [PATCH] Fix gdb/coffread.c build on 32bit architectures
Date: Mon, 28 Aug 2023 08:08:20 -0600 [thread overview]
Message-ID: <87a5ubuunf.fsf@tromey.com> (raw)
In-Reply-To: <20230825211653.2097671-1-mark@klomp.org> (Mark Wielaard's message of "Fri, 25 Aug 2023 23:16:53 +0200")
>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
Hi Mark. Thanks for the patch.
Mark> + error (_("COFF Error: string table offset (%" PRIxPTR ") outside string table (length %ld)"),
gdb doesn't use these PRI macros. Instead you'd write something like:
error ("...%s...", hex_string (value))
Tom
next prev parent reply other threads:[~2023-08-28 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b0896a6-04d4-4c7c-ac32-9ae78acdb66c@redhat.com/>
2023-08-25 21:16 ` Mark Wielaard
2023-08-25 21:19 ` Keith Seitz
2023-08-28 14:08 ` Tom Tromey [this message]
2023-08-28 14:20 ` Keith Seitz
2023-08-28 14:27 ` Keith Seitz
2023-08-28 14:32 ` Mark Wielaard
2023-08-28 14:41 ` Andreas Schwab
2023-08-28 16:31 ` Tom Tromey
2023-08-28 16:33 ` 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=87a5ubuunf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=mark@klomp.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).