Bug 117190 - NPE from recent compiler
Summary: NPE from recent compiler
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 1.5.0RC1   Edit
Assignee: Andrew Clement CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-19 13:26 EST by Ron Bodkin CLA
Modified: 2005-11-23 09:50 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Bodkin CLA 2005-11-19 13:26:00 EST
I wrote this aspect to narrow down another problem and AJDT reported this NPE 
which I think compiles from AspectJ:
aspect Foo {
    declare warning: call(* ApplicationLifecycleAware.startUp
()): "initialization";
    declare warning: call(* startUp(..)): "start up";    
    declare warning: call(* *(..)): "call";    // this line caused it
}


java.lang.NullPointerException
at 
org.aspectj.org.eclipse.jdt.internal.compiler.CompilationResult.computePriority
(CompilationResult.java:121)
at 
org.aspectj.org.eclipse.jdt.internal.compiler.CompilationResult.quickPrioritize
(CompilationResult.java:373)
at org.aspectj.org.eclipse.jdt.internal.compiler.CompilationResult.getProblems
(CompilationResult.java:278)
at 
org.aspectj.org.eclipse.jdt.internal.compiler.CompilationResult.getAllProblems
(CompilationResult.java:169)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager$4.acceptResult
(AjBuildManager.java:872)
at org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.acceptResult
(AjCompilerAdapter.java:239)
at org.aspectj.ajdt.internal.compiler.WeaverAdapter.finishedWith
(WeaverAdapter.java:206)
at org.aspectj.ajdt.internal.compiler.WeaverAdapter.next(WeaverAdapter.java:116)
at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1080)
at org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.weave
(AjCompilerAdapter.java:300)
at org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.afterCompiling
(AjCompilerAdapter.java:178)
at 
org.aspectj.ajdt.internal.compiler.CompilerAdapter.ajc$afterReturning$org_aspect
j_ajdt_internal_compiler_CompilerAdapter$2$f9cc9ca0(CompilerAdapter.aj:70)
at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile
(Compiler.java:367)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation
(AjBuildManager.java:809)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild
(AjBuildManager.java:254)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.incrementalBuild
(AjBuildManager.java:163)
at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:117)
at org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run
(AspectJBuildManager.java:191)

NullPointerException thrown: null
Comment 1 Andrew Clement CLA 2005-11-20 09:24:19 EST
i'll take a look, i've been in there before.
Comment 2 Andrew Clement CLA 2005-11-23 05:27:21 EST
Related to bug 58769.  To do with creating > 100 warnings/errors against a file. This is exactly the same problem but it looks like another route has been taken to creating the CompilationResult ...  

I've checked in what I believe fixes this - waiting on build.
Comment 3 Andrew Clement CLA 2005-11-23 09:50:49 EST
fix available.