This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: java unexpected failures with inexplicable error messages
- From: Tom Tromey <tromey at redhat dot com>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: gcc-bugs at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: 27 Apr 2003 23:35:38 -0600
- Subject: Re: java unexpected failures with inexplicable error messages
- References: <871xzogzb6.fsf@egil.codesourcery.com>
- Reply-to: tromey at redhat dot com
>>>>> "Zack" == Zack Weinberg <zack at codesourcery dot com> writes:
Zack> I'm seeing TestEarlyGC and TestLeak fail in my builds, with
Zack> runtime backtraces like this:
Zack> (1) Are these current expected failures, or did I break something?
Neither; these are fairly new bugs in libgcj. I tracked them down to
a String change I made a while back. I must have missed the
regression somehow. TestLeak clearly shows up in my database as
failing on Apr 1; strangely, TestEarlyGC doesn't start failing until
the 20th.
Anyway, I have a patch for the problem that I'm testing now. I'll
check it in tomorrow, assuming that the test suite really has no
regressions (and the two improvements) tonight.
Zack> (2) What's the deal with this "loaded class X was in fact named X"
Zack> error message? Shouldn't those two strings be, y'know, different?
_Jv_equalUtf8Consts compares the hash values first. The bug was that
we ended up with an incorrect hash value for one of the utf8const
objects.
Tom