[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220907204437.GF9709@brightrain.aerifal.cx>
Date: Wed, 7 Sep 2022 16:44:37 -0400
From: Rich Felker <dalias@...c.org>
To: "Knott, Isabelle" <Isabelle.Knott@....com>
Cc: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: [bug] Cannot fprintf/fwprintf numbers to a wmemstream
On Wed, Sep 07, 2022 at 06:53:06PM +0000, Knott, Isabelle wrote:
> [AMD Official Use Only - General]
>
> Hello, I have found that fprintf or fwprintf fails to write numbers to wmemstreams specifically, and also incorrectly reports how many characters were actually written:
>
> Here is some sample code that reproduces the issue
>
> #include <stddef.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <wchar.h>
>
> int main() {
> wchar_t* buf;
> size_t buf_size;
> FILE* fd = open_wmemstream(&buf, &buf_size);
> if(fd == 0)
> {
> return -1;
> }
> //int chars_written = fprintf(fd, "%d", 40); // this also doesn't work
> int chars_written = fwprintf(fd, L"%d", 40);
> fclose(fd);
> printf("chars_written: %d\n", chars_written);
> printf("buf_size: %ld\n", buf_size);
> fwprintf(stdout, L"expected: \"%d\"\n", 40);
> printf("actual: \"%ls\"\n", buf);
> free(buf);
> return 0;
> }
>
> with musl-gcc compiles from 1.2.3:
>
> chars_written: 2
> buf_size: 0
> expected: "40"
> actual: ""
>
> with glibc 2.35, using fprintf on the wmemstream fails, but fwprintf succeeds, though it won't write to stdout for some reason:
>
> chars_written: 2
> buf_size: 2
> actual: "40"
>
> Thanks!
> -Isabelle
Thanks! This was a really nice find. open_wmemstream intentionally
makes the stream unbuffered, and thereby doesn't even look at buffered
content in its write method, but doesn't take into account the fact
that, per commit bd57e2b43a5b56c00a82adbde0e33e5820c81164, vfprintf
installs a temporary buffer on unbuffered streams to avoid painfully
slow output on unbuffered streams where it would otherwise write a
byte or a field at a time rather than a whole "line" at once.
The attached patch analogous to what open_memstream does should fix
it. I'll commit soon after double-checking that it's right.
Thanks for the clear test case.
Rich
View attachment "fix_wmemstream.diff" of type "text/plain" (579 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
