public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steffen at sdaoden dot eu" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29913] New: iconv(3) is not POSIX compliant, and does not conform to linux man-pages manual Date: Fri, 16 Dec 2022 23:03:28 +0000 [thread overview] Message-ID: <bug-29913-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29913 Bug ID: 29913 Summary: iconv(3) is not POSIX compliant, and does not conform to linux man-pages manual Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: steffen at sdaoden dot eu CC: drepper.fsp at gmail dot com Target Milestone: --- Disclaimer: i have reported this in the past but the issue was closed. The problem is that without //TRANSLIT GNU iconv(3) fails to perform the If iconv( ) encounters a character in the input buffer that is valid, but for which an identical character does not exist in the target codeset, iconv( ) shall perform an implementation-defined conversion on this character. POSIX iconv(3) (Vol. 2: System Interfaces, Issue 7) requirement. Instead GNU libc returns EILSEQ which is wrong as POSIX defined EILSEQ only for [EILSEQ] Input conversion stopped due to an input byte that does not belong to the input codeset. The Linux man-pages 6.01 manual (2022‐10‐09) says the same. But GNU libc _does_ fail for EILSEQ without //TRANSLIT even if the input is valid UTF-8. As can be seen by running this (shortened variant of a config test program). I say "Bye!" already here, and hope it gets fixed! #include <string.h> #include <errno.h> #include <stdio.h> #include <iconv.h> int main(void){ char inb[16], oub[16], *inbp, *oubp; iconv_t id; size_t inl, oul; int rv; memcpy(inbp = inb, "\341\203\276", sizeof("\341\203\276")); inl = sizeof("\341\203\276") -1; oul = sizeof oub; oubp = oub; rv = 1; if((id = iconv_open("us-ascii"/*//TRANSLIT"*/, "utf-8")) == (iconv_t)-1) goto jleave; rv = 14; if(iconv(id, &inbp, &inl, &oubp, &oul) == (size_t)-1) { fprintf(stderr, "error %s %d==%d\n",strerror(errno),errno,errno==EILSEQ); goto jleave; } fprintf(stderr, "bummer\n"); jleave: if(id != (iconv_t)-1) iconv_close(id); return rv; } -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-16 23:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 23:03 steffen at sdaoden dot eu [this message] 2023-02-18 20:48 ` [Bug libc/29913] " rrt at sc3d dot org 2023-02-18 21:20 ` rrt at sc3d dot org 2023-02-18 22:43 ` steffen at sdaoden dot eu 2023-02-19 0:40 ` bruno at clisp dot org 2023-02-19 0:51 ` bruno at clisp dot org 2023-02-19 1:58 ` steffen at sdaoden dot eu 2023-02-19 10:06 ` rrt at sc3d dot org 2023-02-19 10:15 ` rrt at sc3d dot org 2023-02-19 10:22 ` rrt at sc3d dot org 2023-02-19 22:57 ` steffen at sdaoden dot eu 2023-02-19 23:02 ` steffen at sdaoden dot eu 2023-02-20 20:09 ` steffen at sdaoden dot eu 2023-02-20 20:54 ` steffen at sdaoden dot eu 2023-02-20 21:52 ` steffen at sdaoden dot eu
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=bug-29913-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).