Personally, I'm not a HotSpot fan but I do have the latest code and it still
fails.
Try the test sample:
java org.apache.xerces.dom.test 254 works
java org.apache.xerces.dom.test 255 Exception
package org.apache.xerces.dom;
public class test
{
public static void main(String[] argv)
{
int[] n = new int[128];
for(int i=0;i<n.length;i++)n[i]=i*2;
int rc = DeferredDocumentImpl.binarySearch(n, 0, 128,
Integer.parseInt(argv[0]));
System.out.println("Index: "+rc);
}
}
george
-----Original Message-----
From: Andy Clark [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2000 2:48 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBoundsException: 128
"George T. Joseph" wrote:
>
> Don't be so quick to blame HotSpot here!! This fails with Karen's files on
Sun
> win32 1.2.2 both classic and HotSpot and also on IBM Win32 1.1.8.
We've had a lot of problem with HotSpot causing people to report
false bugs. HotSpot *does* have problems because most of our
bugs reported regarding array index out of bounds goes away when
they turn HotSpot off.
We are just trying to save support time by having the customer
try not using HotSpot before we look into the problem. If the
problem persists (which is what I asked Karen to tell me) then
we can look into it.
Seeing as how the problem *does* persist, I went to the CVS
log for DeferredDocumentImpl.java and found out that I fixed
this problem in revision 1.5 of the file but revision 1.3 is
in the Xerces 1.0.1 build. Therefore, to fix this problem,
please a) extract and build the latest sources from the CVS
repository, or b) wait for the next release.
--
Andy Clark * IBM, JTC - Silicon Valley * [EMAIL PROTECTED]
