Bug 84215 - ArrayIndexOutOfBoundsException, internal compiler error
Summary: ArrayIndexOutOfBoundsException, internal compiler error
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: 3.1 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 84334 84553 85209 85666 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-02 06:25 EST by Joris Verschoor CLA
Modified: 2005-02-17 15:13 EST (History)
4 users (show)

See Also:


Attachments
logfile with stacktraces (14.07 KB, text/plain)
2005-02-02 06:26 EST, Joris Verschoor CLA
no flags Details
test project (2.94 KB, application/octet-stream)
2005-02-02 08:49 EST, Joris Verschoor CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joris Verschoor CLA 2005-02-02 06:25:19 EST
I'm using eclipse M4, and this sometimes pops by..

I also use eclipseme, but I'm not aware that it changes any sourcecode.. After 
cleaning my project / rebuilding / restarting eclipse, the problem still 
exists..

I also removes the cldc builder (eclipseme)

When I open the file where it happens, I get some popups telling me "AST 
creation failed"
Comment 1 Joris Verschoor CLA 2005-02-02 06:26:00 EST
Created attachment 17622 [details]
logfile with stacktraces
Comment 2 Philipe Mulet CLA 2005-02-02 07:03:17 EST
Could you please provide steps to reproduce and then reopen ?

This problem is likely internal to the file where it is reported. Attaching the
source of the offending file should be sufficient to get started. 
When building, there should be a fake problem in problem view recording the
compiler failure associated to line 1. This would point at the offending file.
Comment 3 Joris Verschoor CLA 2005-02-02 08:48:32 EST
I've created a new project, and removed my sjpp encoding trick.
The error happens when I set the jdk compliance to any non-5.0 and  uncheck 
the "Inline finally blocks" (I do this to reduce class file size, as I'm 
working on midlets..

I've trimmed down the source, and it's very weird... When I come to a certain 
size, when I remove some a method or field, the error goes away. If I put it 
back, the error is back.. 
Comment 4 Joris Verschoor CLA 2005-02-02 08:49:18 EST
Created attachment 17624 [details]
test project

use any non-5.0 jdk, and uncheck the inline finally checkbox
Comment 5 Joris Verschoor CLA 2005-02-02 09:00:45 EST
The test project I've created also gives the error on another M4 installation I 
have (other workstation) 
Also, I've tried it with the latest integration build. eclipse-SDK-I20050202-
0800-win32. Clean install, no cutomizations.
Comment 6 Joris Verschoor CLA 2005-02-02 09:02:46 EST
-SDK-I20050202-0800-win32 .log snippet:

!SESSION 2005-02-02 15:00:05.83 ------------------------------------------------
eclipse.buildId=I20050202-0800
java.version=1.5.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 4 2 2005-02-02 15:00:05.99
!MESSAGE Problems occurred when invoking code from plug-
in: "org.eclipse.core.resources".
!STACK 0
java.lang.ArrayIndexOutOfBoundsException
	at java.lang.System.arraycopy(Native Method)
	at org.eclipse.jdt.internal.compiler.flow.UnconditionalFlowInfo.copy
(UnconditionalFlowInfo.java:197)
	at 
org.eclipse.jdt.internal.compiler.flow.ExceptionHandlingFlowContext.recordReturn
From(ExceptionHandlingFlowContext.java:182)
	at org.eclipse.jdt.internal.compiler.ast.ReturnStatement.analyseCode
(ReturnStatement.java:60)
	at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode
(Block.java:40)
Comment 7 Philipe Mulet CLA 2005-02-02 10:00:56 EST
Reproduced. Thanks for testcase.

 
Comment 8 Philipe Mulet CLA 2005-02-02 10:57:28 EST
Problem comes from non redimensionning defNull /defNonNull for extra inits in
certain circumstances. 
Added AssignmentTest#test034.

Fixed

NOTE: reason for the problem sometimes being revealed or not, is due to the fact
we have optimized support for 64 first variables. The bug was visible under some
circumstances and only if you had more than 64 variables.
Comment 9 Philipe Mulet CLA 2005-02-03 10:38:55 EST
*** Bug 84334 has been marked as a duplicate of this bug. ***
Comment 10 Olivier Thomann CLA 2005-02-07 10:01:18 EST
*** Bug 84553 has been marked as a duplicate of this bug. ***
Comment 11 Olivier Thomann CLA 2005-02-14 22:18:37 EST
*** Bug 85209 has been marked as a duplicate of this bug. ***
Comment 12 Jerome Lanneluc CLA 2005-02-15 13:09:21 EST
Verified in I20050215-0800
Comment 13 Philipe Mulet CLA 2005-02-17 07:01:14 EST
*** Bug 85666 has been marked as a duplicate of this bug. ***
Comment 14 Keith Cochran CLA 2005-02-17 15:13:41 EST
Works for me now using the I20050217-1200 integration build.