Bug 488362 - ArrayIndexOutOfBoundsException in InferenceContext18.checkExpression(InferenceContext18.java:755)
Summary: ArrayIndexOutOfBoundsException in InferenceContext18.checkExpression(Inferenc...
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.8.9   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-24 03:19 EST by Kamil Ledzion CLA
Modified: 2016-03-08 12:12 EST (History)
1 user (show)

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 Kamil Ledzion CLA 2016-02-24 03:19:45 EST 
java.lang.ArrayIndexOutOfBoundsException
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.checkExpression(InferenceContext18.java:755)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.moreSpecificMain(InferenceContext18.java:710)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.isMoreSpecificThan(InferenceContext18.java:658)
at org.aspectj.org.eclipse.jdt.internal. ... ldJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Compile error: ArrayIndexOutOfBoundsException thrown: 0
Comment 1 Andrew Clement CLA 2016-02-26 01:49:32 EST 
Any relation to bug 468886 I wonder, similar area of the code.
Comment 2 Kamil Ledzion CLA 2016-02-26 02:28:25 EST 
Yes, I guess it is the same issue.
Comment 3 Andrew Clement CLA 2016-03-08 12:12:49 EST 
Searching JDT bugs revealed this very similar sounding one, bug 469587, which is a dup of bug 461004. I've run the testcode in these bugs against current AspectJ and they don't fail - so we already include the fixes. So I guess i should confirm what version you are running?  If this happens to you again and you are in eclipse can you confirm the version of AspectJ/AJDT you are using. It is possible you are on a release version of AJDT that has the problem whereas the latest AJDT snapshots would not, because they have an up to date AspectJ.