Bug 84334 - ArrayIndexOutOfBoundsException when compiling Parser.java
Summary: ArrayIndexOutOfBoundsException when compiling Parser.java
Status: RESOLVED DUPLICATE of bug 84215
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-03 10:23 EST by David Audel CLA
Modified: 2005-02-03 10:42 EST (History)
0 users

See Also:


Attachments
Parser.java (355.99 KB, text/plain)
2005-02-03 10:26 EST, David Audel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Audel CLA 2005-02-03 10:23:56 EST
build I20050202-0800

1) create a fresh workspace
2) checkout jdtcore plugin
3) replace Parser.java with the content of the attached file
4) compile

there is an ArrayIndexOutOfBoundsException in .log

java.lang.ArrayIndexOutOfBoundsException
	at
org.eclipse.jdt.internal.compiler.flow.UnconditionalFlowInfo.copy(UnconditionalFlowInfo.java:197)
	at
org.eclipse.jdt.internal.compiler.flow.ExceptionHandlingFlowContext.recordHandlingException(ExceptionHandlingFlowContext.java:175)
	at
org.eclipse.jdt.internal.compiler.flow.FlowContext.checkExceptionHandlers(FlowContext.java:105)
	at
org.eclipse.jdt.internal.compiler.ast.MessageSend.analyseCode(MessageSend.java:53)
	at
org.eclipse.jdt.internal.compiler.ast.SingleNameReference.analyseAssignment(SingleNameReference.java:66)
	at org.eclipse.jdt.internal.compiler.ast.Assignment.analyseCode(Assignment.java:51)
	at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:40)
	at
org.eclipse.jdt.internal.compiler.ast.TryStatement.analyseCode(TryStatement.java:108)
	at
org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.analyseCode(MethodDeclaration.java:82)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.internalAnalyseCode(TypeDeclaration.java:701)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.analyseCode(TypeDeclaration.java:264)
	at
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.analyseCode(CompilationUnitDeclaration.java:80)
	at org.eclipse.jdt.internal.compiler.Compiler.resolve(Compiler.java:569)
	at org.eclipse.jdt.internal.compiler.Compiler.resolve(Compiler.java:610)
	at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:165)
	at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:212)
	at
org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:78)
	at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:710)
	at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:761)
	at
org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1078)
	at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:91)
	at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:133)
	at
org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86)
	at
org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:94)
	at org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:75)
	at org.eclipse.jdt.internal.ui.text.JavaReconciler.process(JavaReconciler.java:318)
	at
org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:204)
Comment 1 David Audel CLA 2005-02-03 10:26:25 EST
Created attachment 17654 [details]
Parser.java
Comment 2 Olivier Thomann CLA 2005-02-03 10:32:03 EST
I believe this is a duplicate of bug 84215.
Could you please try with latest?
Comment 3 Philipe Mulet CLA 2005-02-03 10:38:55 EST

*** This bug has been marked as a duplicate of 84215 ***
Comment 4 David Audel CLA 2005-02-03 10:42:37 EST
The problem doesn't occur with I20050202-0800 + jdtcore head.