From: Bruno Haible <bruno@clisp.org>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] swprintf: count returned by %n is wrong after conversion error
Date: Mon, 20 Mar 2023 19:22:25 +0100 [thread overview]
Message-ID: <3481517.K71DO8KEF6@nimes> (raw)
In-Reply-To: <20230320180842.GS4163@brightrain.aerifal.cx>
Rich Felker wrote:
> There is probably also a similar issue in non-wide printf, but only
> for write errors, not for encoding errors, and only visibly wrong if
> the write error is transient (e.g. EAGAIN).
Glad that you are seeing this by code inspection. Because in my test
suite, I only test the behaviour in case of encoding errors, not of
write errors.
Bruno
next prev parent reply other threads:[~2023-03-20 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 23:48 Bruno Haible
2023-03-20 12:15 ` Rich Felker
2023-03-20 18:08 ` Rich Felker
2023-03-20 18:22 ` Bruno Haible [this message]
2023-03-20 21:19 ` Rich Felker
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=3481517.K71DO8KEF6@nimes \
--to=bruno@clisp.org \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).