public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: olivier@zipworld.com.au To: gcc-gnats@gcc.gnu.org Subject: java/5134: bug in gnu.gcj.runtime.StringBuffer Date: Sun, 16 Dec 2001 13:46:00 -0000 [thread overview] Message-ID: <20011216213523.10060.qmail@sources.redhat.com> (raw) >Number: 5134 >Category: java >Synopsis: bug in gnu.gcj.runtime.StringBuffer >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Dec 16 13:46:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: olivier@zipworld.com.au >Release: gcc version 3.1 20011211 (experimental) >Organization: >Environment: Reading specs from /usr/local/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs Configured with: ../../program/cvs/gcc/configure --prefix=/usr/local/gcc --enable-shared --enable-threads=posix --enable-languages=c++,java Thread model: posix gcc version 3.1 20011211 (experimental) >Description: gcj does not handle correctly the concatenation of two String in some cases (see attached example). gcj calls a gnu.gcj.runtime.StringBuffer and then throws an .ArrayIndexOutOfBoundsException!!! This seems to happen only when the two String exceed 34 characters. With one less character, the example code works. >How-To-Repeat: gcj --main=A A.java ./a.out >Fix: Unknown... >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="A.java" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="A.java" cHVibGljIGNsYXNzIEEgCnsKICAgcHVibGljIHN0YXRpYyB2b2lkIG1haW4oU3RyaW5nW10gYXJn cykgCiAgIHsKICAgICAgU3RyaW5nIGEgPSAiMDEiOwogICAgICBTdHJpbmcgYiA9ICIyMzQ1Njc4 OTAxMjM0NTY3ODkwMTIzNDU2Nzg5MDEyMzQiOwogICAgICBhID0gYSArIGI7CiAgICAgIFN5c3Rl bS5vdXQucHJpbnRsbihhKTsKICAgfQp9Cg==
next reply other threads:[~2001-12-16 21:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-16 13:46 olivier [this message] 2001-12-16 14:36 tromey
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=20011216213523.10060.qmail@sources.redhat.com \ --to=olivier@zipworld.com.au \ --cc=gcc-gnats@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).