public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "serg at vostok dot net" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/31939] New: Command line arguments are byteswapped before being passed to the program runing in custom locale. Date: Tue, 15 May 2007 16:35:00 -0000 [thread overview] Message-ID: <bug-31939-14546@http.gcc.gnu.org/bugzilla/> (raw) Conversion to UCS-2 encoding in GNU libiconv returns bytes in network order. gcj wants to have them in host order. The hack in libgcj swaps bytes when necessary. However, command line arguments slip by the swapper (or go through it even number of times). This produces unrecognizable for a program command line arguments. There is a non-zero probability of this producing invalid UTF-16 strings, e.g. with unpaired surrogates. That, in turn, may result in segmentation faults during string operations, especially I/O character encoding conversion. -- Summary: Command line arguments are byteswapped before being passed to the program runing in custom locale. Product: gcc Version: 4.1.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: serg at vostok dot net GCC build triplet: i386-portbld-freebsd6.2 GCC host triplet: i386-portbld-freebsd6.2 GCC target triplet: i386-portbld-freebsd6.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31939
next reply other threads:[~2007-05-15 16:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-15 16:35 serg at vostok dot net [this message] 2007-05-15 17:05 ` [Bug libgcj/31939] " serg at vostok dot net 2007-05-15 17:11 ` serg at vostok dot net 2007-05-15 17:33 ` serg at vostok dot net 2007-05-18 19:07 ` serg at vostok dot net
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-31939-14546@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.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).