mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Bruno Haible <bruno@clisp.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] swprintf %lc directive does not work for some wide characters
Date: Mon, 12 Jun 2023 16:27:28 -0400	[thread overview]
Message-ID: <20230612202728.GB4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <2976941.0vhOF50zNu@nimes>

On Mon, Jun 12, 2023 at 04:44:44PM +0200, Bruno Haible wrote:
> According to ISO C 11 § 7.29.2.1, in the *wprintf family of functions, the
> %lc directive works like this:
>   "[If an l length modifier is present,] the wint_t argument is converted to
>    wchar_t and written."
> 
> Likewise in ISO C 17 § 7.29.2 and ISO C 23 § 7.31.2.1 and in POSIX:2018
> <https://pubs.opengroup.org/onlinepubs/9699919799/functions/fwprintf.html>.
> 
> In musl libc 1.2.4 (as part of Alpine Linux 3.18.0) this does not work for
> some characters.
> 
> How to reproduce:
> =================================== foo.c ===================================
> #include <stdio.h>
> #include <wchar.h>
> int main ()
> {
>   static wint_t L_invalid = (wchar_t) 0x76543210;
>   wchar_t buf[3];
>   int ret = swprintf (buf, 3, L"%lc", L_invalid);
>   if (ret >= 0)
>     fprintf (stderr, "OK, %d characters\n", ret);
>   else
>     perror ("swprintf failed");
> }
> =============================================================================
> $ gcc -Wall foo.c
> $ ./a.out
> 
> Expected output:
> OK, 1 characters
> 
> Actual output:
> swprintf failed: Illegal byte sequence
> 
> 

Per my reading of the specification, this is not a bug but is the
expected behavior.

    In addition, all forms of fwprintf() shall fail if:

    [EILSEQ]
            A wide-character code that does not correspond to a valid
            character has been detected.

Since the language "has been detected" is used here, this seems to
allow for an implementation not to make it an error if the condition
is not "detected". We make it an error because all wide stdio takes
place through a byte-oriented buffer, and the conversions back and
forth inherently "detect" the condition and have no way to pass the
invalid wchar_t thru. There is no concept of directly writing wide
characters.

Note that the error here is happening not as part of the conversion
specifier, but the output operation.

Rich

  reply	other threads:[~2023-06-12 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 14:44 Bruno Haible
2023-06-12 20:27 ` Rich Felker [this message]
2023-06-12 20:53   ` Bruno Haible
2023-06-12 21:28     ` 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=20230612202728.GB4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=bruno@clisp.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).