From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eggert@cs.ucla.edu, 8435@debbugs.gnu.org
Subject: bug#8435: misuse of error ("...%d...", ...) on 64-bit hosts
Date: Sun, 10 Apr 2011 01:19:25 -0400 [thread overview]
Message-ID: <E1Q8n3V-0003Rm-2m@fencepost.gnu.org> (raw)
In-Reply-To: <jwvoc4e69xi.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 10 Apr 2011 00:52:09 -0300)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 8435@debbugs.gnu.org
> Date: Sun, 10 Apr 2011 00:52:09 -0300
>
> If the problematic case can be detected easily, that's good enough.
What would you suggest to do if we detect it? To recap, this is in
the context of `message' or `error' called to produce a message about
something.
> I don't understand the problem enough (haven't dug into it yet) to know
> if that's the case.
There are two issues:
. %c used to display a non-ASCII character, when the data points to a
multibyte sequence. doprnt converts the data to a wide character,
when it displays the message, vsnprintf does not.
. If the buffer supplied to doprnt is too small, it takes care to
truncate the text only on character boundaries, whereas vsnprintf
will not.
next prev parent reply other threads:[~2011-04-10 5:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 19:59 bug#8435: misuse of error ("...%d...", ...) on 64-bit hosts Paul Eggert
[not found] ` <handler.8435.B.130211997010029.ack@debbugs.gnu.org>
2011-04-07 7:33 ` Paul Eggert
2011-04-07 12:29 ` Andy Moreton
2011-04-07 18:31 ` Eli Zaretskii
2011-04-07 20:43 ` Paul Eggert
2011-04-08 8:58 ` Eli Zaretskii
2011-04-08 23:34 ` Paul Eggert
2011-04-09 7:20 ` Eli Zaretskii
2011-04-09 18:24 ` Paul Eggert
2011-04-09 18:32 ` Eli Zaretskii
2011-04-09 19:39 ` Paul Eggert
2011-04-09 20:21 ` Eli Zaretskii
2011-04-10 3:52 ` Stefan Monnier
2011-04-10 5:19 ` Eli Zaretskii [this message]
2011-04-11 1:44 ` Stefan Monnier
2011-04-11 2:54 ` Eli Zaretskii
2011-04-10 17:03 ` Paul Eggert
2011-04-09 19:28 ` Eli Zaretskii
2011-04-09 19:43 ` Paul Eggert
2011-04-08 23:37 ` Paul Eggert
2011-04-25 0:59 ` Daniel Colascione
2011-04-25 6:42 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Q8n3V-0003Rm-2m@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=8435@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).