Bug 121384 - Internal compiler error: NullPointerException in AsmRelationshipProvider.java:131
Summary: Internal compiler error: NullPointerException in AsmRelationshipProvider.java...
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.5.0RC1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.5.0   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-19 05:29 EST by Matt Chapman CLA
Modified: 2005-12-21 04:28 EST (History)
0 users

See Also:


Attachments
testcase (2.84 KB, application/octet-stream)
2005-12-19 05:32 EST, Matt Chapman CLA
no flags Details
testcase part 2 (871 bytes, text/plain)
2005-12-19 05:33 EST, Matt Chapman CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Chapman CLA 2005-12-19 05:29:53 EST
Incremental compilation issue from the list:

java.lang.NullPointerException
at org.aspectj.weaver.AsmRelationshipProvider.addDeclareParentsRelationship(AsmRelationshipProvider.java:131)
at org.aspectj.ajdt.internal.compiler.lookup.AjLookupEnvironment.doDeclareParents(AjLookupEnvironment.java:694)
at org.aspectj.ajdt.internal.compiler.lookup.AjLookupEnvironment.weaveInterTypeDeclarations(AjLookupEnvironment.java:561)
at org.aspectj.ajdt.internal.compiler.lookup.AjLookupEnvironment.weaveInterTypeDeclarations(AjLookupEnvironment.java:498)
at org.aspectj.ajdt.internal.compiler.lookup.AjLookupEnvironment.createBinaryTypeFrom(AjLookupEnvironment.java:983)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:480)
at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.accept(Compiler.java:190)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:137)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage(PackageBinding.java:178)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findImport(CompilationUnitScope.java:413)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findSingleImport(CompilationUnitScope.java:466)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInImports(CompilationUnitScope.java:331)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInTypes(CompilationUnitScope.java:400)
at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:507)
at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:329)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:811)
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

Testcase and steps to reproduce to follow...
Comment 1 Matt Chapman CLA 2005-12-19 05:32:40 EST
Created attachment 31940 [details]
testcase

Step 1: Create a project with the attached. It should build without errors.
Comment 2 Andrew Clement CLA 2005-12-19 05:33:09 EST
I suspect this is related to a null sourcelocation coming into the method in the case of an @Decp.
Comment 3 Matt Chapman CLA 2005-12-19 05:33:58 EST
Created attachment 31941 [details]
testcase part 2

Step 2: Add the attached source file to the project, such that an incremental compile is triggered. The NPE should now occur.
Comment 4 Andrew Clement CLA 2005-12-19 06:24:24 EST
i've recreated this in our multi project test harness.
Comment 5 Andrew Clement CLA 2005-12-19 10:12:01 EST
Fix checked in - we just have to make sure a source location is set for the decp.  There is a bigger piece of work to make the the source locations for annotation style behave the same as for code style.
Comment 6 Andrew Clement CLA 2005-12-21 04:28:57 EST
fix available.