mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Broken freopen() does not reset fwide()
Date: Wed, 17 Aug 2022 18:38:52 -0400	[thread overview]
Message-ID: <20220817223848.GE7074@brightrain.aerifal.cx> (raw)
In-Reply-To: <20220817151131.GB7074@brightrain.aerifal.cx>

On Wed, Aug 17, 2022 at 11:11:31AM -0400, Rich Felker wrote:
> On Tue, Aug 16, 2022 at 06:33:35PM +0000, Anonymousemail wrote:
> >    Powered by Anonymousemail → [1]Join Us!
> > 
> >    I'm using musl based distribution.
> >    The official example from https://en.cppreference.com/w/c/io/fwide is
> >    malfunctioning, musl does not reset the fwide(), returns -1 (meaning BYTE
> >    oriented).
> > 
> >    Output from example on musl:
> >    1) A newly opened stream has no orientation.
> >        no orientation
> >    2) Establish byte orientation.
> >        narrow orientation
> >        narrow character read '#'
> >        wide character read 'i'
> >    3) Only freopen() can reset stream orientation.
> >    4) A reopened stream has no orientation.
> >        narrow orientation  <- problem detected here, should say "no
> >    orientation"
> >    5) Establish wide orientation.
> >        narrow orientation
> >        narrow character read '#'
> >        wide character read 'i'
> > 
> >    Another simple example to reproduce the issue.:
> >    #include <stdio.h>
> >    #include <wchar.h>
> >    #include <stdlib.h> // for EXIT_SUCCESS
> >    #include <assert.h>
> > 
> >    int main() {
> >        enum { narrow = -1, query = 0, wide = 1 };
> >        FILE* test = fopen("test.bin", "r");
> >        if(!test) {
> >            puts("You need to have test.bin file.");
> >            abort();
> >        }
> >        // establish NARROW orientation
> >        fwide(test, narrow);
> >        // reopen to reset, broken on musl
> >        freopen("test.bin", "r", test);
> >        assert(fwide(test, query) == 0); // will fail on musl
> >        // CLEANUP
> >        fclose(test);
> >        // Exit the program
> >        return EXIT_SUCCESS;
> >    }
> > 
> >    -----
> >    Save as main.c, run with
> >    cc main.c
> >    echo test >test.bin
> >    ../a.out
> > 
> >    Will output
> >    Assertion failed: fwide(test, query) == 0 (main2.c: main: 17)
> >    Aborted
> 
> Indeed this looks like an oversight. I'll need to look at what it will
> take to fix it. Naively, just f->wide = 0 before successful return in
> freopen seems ok, but probably also f->locale needs to be set to 0 to
> reset the encoding rule, and it might be necessary to null out some
> buffer pointers to force future calls to stdio functions to reprobe
> the width.
> 
> Thanks for the report.
> 
> BTW is there a way you can fix the mailer you're using? The plain text
> version of your mail was not plain text, but was littered with html
> entities (&nbsp; etc.) making it unreadable, so I rendered the html
> version to text in order to be able to reply.

OK, fflush took care of the buffer pointers already, so just setting
f->mode and f->locale to 0 should be fine. I'll commit a fix.

Rich

      reply	other threads:[~2022-08-17 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 18:33 Anonymousemail
2022-08-17 15:11 ` Rich Felker
2022-08-17 22:38   ` Rich Felker [this message]

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=20220817223848.GE7074@brightrain.aerifal.cx \
    --to=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).