Bug 9726 - array out of bounds during build
Summary: array out of bounds during build
Status: RESOLVED DUPLICATE of bug 9476
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-13 13:55 EST by John Arthorne CLA
Modified: 2003-03-17 11:57 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2002-02-13 13:55:01 EST 
Build 20020212

I have a self-hosting workspace, with core + org.eclipse.ui as source, and all 
other projects as binary.  I did a synchronize with stream which triggered an 
incremental build.  This was the first build after upgrading to the latest 
drop, so it triggered the restoring of builder state.  Sometime during the build 
the following stack trace appeared on the console.  Note that there was no error 
dialog and nothing in the log, just a stack on the console.  I have not been 
able to reproduce it.

java.lang.ArrayIndexOutOfBoundsException: 3407872
        at org.eclipse.jdt.internal.core.newbuilder.State.read(State.java(Compil
ed Code))
        at org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.readState(JavaBu
ilder.java:59)
        at org.eclipse.jdt.internal.core.JavaModelManager.readState(JavaModelMan
ager.java:846)
        at org.eclipse.jdt.internal.core.JavaModelManager.getLastBuiltState(Java
ModelManager.java:634)
        at org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.getLastState(Jav
aBuilder.java:216)
        at org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.build(JavaBuilde
r.java:84)
        at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java
:351)
        at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfo
rm.java:817)
        at org.eclipse.core.runtime.Platform.run(Platform.java:395)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:109)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:174)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:184)
        at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java
:133)
        at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfo
rm.java:817)
        at org.eclipse.core.runtime.Platform.run(Platform.java:395)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:147)
        at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java
:209)
        at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.
java:701)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1237
)
        at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOp
eration.java:78)
        at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(Modal
Context.java:98)
org.eclipse.core.runtime.CoreException[2]: java.lang.ArrayIndexOutOfBoundsExcept
ion: 3407872
        at org.eclipse.jdt.internal.core.newbuilder.State.read(State.java(Compil
ed Code))
        at org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.readState(JavaBu
ilder.java:59)
        at org.eclipse.jdt.internal.core.JavaModelManager.readState(JavaModelMan
ager.java:846)
        at org.eclipse.jdt.internal.core.JavaModelManager.getLastBuiltState(Java
ModelManager.java:634)
        at org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.getLastState(Jav
aBuilder.java:216)
        at org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.build(JavaBuilde
r.java:84)
        at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java
:351)
        at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfo
rm.java:817)
        at org.eclipse.core.runtime.Platform.run(Platform.java:395)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:109)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:174)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:184)
        at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java
:133)
        at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfo
rm.java:817)
        at org.eclipse.core.runtime.Platform.run(Platform.java:395)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager
.java:147)
        at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java
:209)
        at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.
java:701)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1237
)
        at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOp
eration.java:78)
        at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(Modal
Context.java:98)
Comment 1 Philipe Mulet CLA 2002-02-13 17:27:24 EST 
Was this your first build after restarting with a 20020212 build ? We had a bug 
in the previous builds which could have caused the built state to be 
incorrectly serialized.
Comment 2 John Arthorne CLA 2002-02-13 18:22:37 EST 
Yes, this was the first build after restarting with 20020212.
Comment 3 Kent Johnson CLA 2002-02-14 11:58:00 EST 

*** This bug has been marked as a duplicate of 9476 ***