Community
Participate
Working Groups
Got the following exception during startup of Eclipse java.lang.ArrayIndexOutOfBoundsException at org.aspectj.ajdt.internal.core.builder.EclipseAdapterUtils.makeLocationContext(EclipseAdapterUtils.java:65) at org.aspectj.ajdt.internal.core.builder.EclipseAdapterUtils.makeSourceLocation(EclipseAdapterUtils.java:121) at org.aspectj.ajdt.internal.core.builder.EclipseAdapterUtils.makeMessage(EclipseAdapterUtils.java:130) at org.aspectj.ajdt.internal.core.builder.AjBuildManager$4.acceptResult(AjBuildManager.java:959) at org.aspectj.ajdt.internal.compiler.AjPipeliningCompilerAdapter.acceptResult(AjPipeliningCompilerAdapter.java:402) at org.aspectj.ajdt.internal.compiler.AjPipeliningCompilerAdapter.afterProcessing(AjPipeliningCompilerAdapter.java:375) at org.aspectj.ajdt.internal.compiler.CompilerAdapter.ajc$after$org_aspectj_ajdt_internal_compiler_CompilerAdapter$5$6b855184(CompilerAdapter.aj:98) at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:533) at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:329) at org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:891) at org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:246) at org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:165) at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:122) at org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:191) ArrayIndexOutOfBoundsException thrown: -2
passing over to compiler
If this is a constant problem, a temporary workaround may be: -Xset:pipelineCompilation=false in the 'other > options' for your workspace or projects.
A test project for this scenario would be useful. Without one I can merely guard on it occurring but that may mean in AJDT that we start to lose some of the contextual information that appears (it is possible some of the red squigglies may go missing or appear in funny places). I guess the best we can do is guard for now and fix that when a simpler test scenario can be created.
guard committed.
Andy, are you asking for a test project from me?
hmmm, only half seriously because I imagine it would be hard for you to create one? I've put the guard in, maybe we should make do with that - and if we get bug reports in about incorrect error messages we can investigate further at that time.
Great, because (sadly) I wouldn't be able to share my projects or workspace. Will the guard for this section of code be in the next development version or how does this work?
it'll be in the next dev version of AspectJ - then AJDT a few days later. if its always happening, try the workaround I suggest in comment #2.
is this all working for you now? can I close the bug?
seems to working for me now. haven't experienced it for a while
ok, let's consider it fixed. As usual, reopen if you see something like this again... thanks for responding so quickly.
