From: "H. J. Lu" <hjl@lucon.org>
To: Andreas Schwab <schwab@suse.de>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: Use generic_print_address for address
Date: Sun, 13 Feb 2005 12:44:00 -0000 [thread overview]
Message-ID: <20050212002320.GA11480@lucon.org> (raw)
In-Reply-To: <jesm42mz2z.fsf@sykes.suse.de>
On Sat, Feb 12, 2005 at 12:55:16AM +0100, Andreas Schwab wrote:
> "H. J. Lu" <hjl@lucon.org> writes:
>
> > On Sat, Feb 12, 2005 at 12:39:12AM +0100, Andreas Schwab wrote:
> >> "H. J. Lu" <hjl@lucon.org> writes:
> >>
> >> > + info->fprintf_func (info->stream, _("Address 0x"));
> >> > + generic_print_address (memaddr, info);
> >> > + info->fprintf_func (info->stream, _(" is out of bounds.\n"));
> >>
> >> This is very i18n unfriendly.
> >>
> >
> > Do you have any suggestions?
>
> If there is a way to format the address into a buffer then the format
> string can be combined again.
>
Like this?
H.J.
----
2005-02-11 H.J. Lu <hongjiu.lu@intel.com>
* dis-buf.c (perror_memory): Use sprintf_vma to print out
address.
--- opcodes/dis-buf.c.vma 2003-11-17 12:30:30.000000000 -0800
+++ opcodes/dis-buf.c 2005-02-11 16:20:38.508542555 -0800
@@ -56,10 +56,15 @@ perror_memory (status, memaddr, info)
/* Can't happen. */
info->fprintf_func (info->stream, _("Unknown error %d\n"), status);
else
- /* Actually, address between memaddr and memaddr + len was
- out of bounds. */
- info->fprintf_func (info->stream,
- _("Address 0x%x is out of bounds.\n"), memaddr);
+ {
+ char buf[30];
+
+ /* Actually, address between memaddr and memaddr + len was
+ out of bounds. */
+ sprintf_vma (buf, memaddr);
+ info->fprintf_func (info->stream,
+ _("Address 0x%s is out of bounds.\n"), buf);
+ }
}
/* This could be in a separate file, to save miniscule amounts of space
next prev parent reply other threads:[~2005-02-12 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 10:46 H. J. Lu
2005-02-13 2:06 ` Andreas Schwab
[not found] ` <20050211234902.GA11119@lucon.org>
[not found] ` <jesm42mz2z.fsf@sykes.suse.de>
2005-02-13 12:44 ` H. J. Lu [this message]
2005-02-14 14:58 ` Nick Clifton
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=20050212002320.GA11480@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=schwab@suse.de \
/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).