public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ezyang at mit dot edu" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13517] New: iconv generates spurious warnings even though //IGNORE is set Date: Sun, 18 Dec 2011 22:33:00 -0000 [thread overview] Message-ID: <bug-13517-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13517 Bug #: 13517 Summary: iconv generates spurious warnings even though //IGNORE is set Product: glibc Version: 2.14 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: ezyang@mit.edu Classification: Unclassified iconv generates spurious warnings when unconvertible sequences are encountered while IGNORE is enabled. Expected behavior (from libiconv-1.14): ezyang@javelin:~/Dev/glibc/build$ printf "\xc3\xbc\x73" | ~/Desktop/libiconv-1.14/src/iconv_no_i18n -f utf-8 -t ascii//IGNORE s Actual behavior (from latest Git glibc-2.14-567-ga4647e7): ezyang@javelin:~/Dev/glibc/build$ printf "\xc3\xbc\x73" | ./testrun.sh iconv/iconv_prog -f utf-8 -t ascii//IGNORE siconv/iconv_prog: illegal input sequence at position 5 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-12-18 22:33 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-18 22:33 ezyang at mit dot edu [this message] 2011-12-22 23:44 ` [Bug libc/13517] " drepper.fsp at gmail dot com 2014-06-27 11:27 ` fweimer at redhat dot com
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-13517-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: 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).