Bug 98460 - [inc-compilation] NPE when compiling (ResolvedTypeX.java:258)
Summary: [inc-compilation] NPE when compiling (ResolvedTypeX.java:258)
Status: RESOLVED WORKSFORME
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.5.0 M4   Edit
Assignee: Andrew Clement CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-05 22:17 EDT by Barry Kaplan CLA
Modified: 2005-10-28 09:41 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barry Kaplan CLA 2005-06-05 22:17:22 EDT
(eclipse 3.1.M7, ajdt 20050525133001)

Can't really provide much context. I had many errors in the aspect, removed most
of the code (so that it no longer had errors) and saved. That was when I got the
NPR. Then I did a full clean-build, and all errors were removed.

This is pretty common for me. Seems that ajdt does not always compile everything
it should, or not correctly, on file saves. Generally clean-build puts things right.

----
java.lang.NullPointerException
at org.aspectj.weaver.ResolvedTypeX.addAndRecurse(ResolvedTypeX.java:258)
at org.aspectj.weaver.ResolvedTypeX.addAndRecurse(ResolvedTypeX.java:259)
at
org.aspectj.weaver.ResolvedTypeX.getMethodsWithoutIterator(ResolvedTypeX.java:253)
at
org.aspectj.weaver.bcel.BcelTypeMunger.enforceDecpRule1_abstractMethodsImplemented(BcelTypeMunger.java:208)
at org.aspectj.weaver.bcel.BcelTypeMunger.mungeNewParent(BcelTypeMunger.java:174)
at org.aspectj.weaver.bcel.BcelTypeMunger.munge(BcelTypeMunger.java:89)
at org.aspectj.weaver.bcel.BcelClassWeaver.weave(BcelClassWeaver.java:345)
at org.aspectj.weaver.bcel.BcelClassWeaver.weave(BcelClassWeaver.java:95)
at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1377)
at org.aspectj.weaver.bcel.BcelWeaver.weaveWithoutDump(BcelWeaver.java:1342)
at org.aspectj.weaver.bcel.BcelWeaver.weaveAndNotify(BcelWeaver.java:1120)
at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1006)
at
org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.weave(AjCompilerAdapter.java:286)
at
org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.afterCompiling(AjCompilerAdapter.java:165)
at
org.aspectj.ajdt.internal.compiler.CompilerAdapter.ajc$afterReturning$org_aspectj_ajdt_internal_compiler_CompilerAdapter$2$f9cc9ca0(CompilerAdapter.aj:70)
at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:368)
at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:727)
at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:229)
at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.incrementalBuild(AjBuildManager.java:147)
at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:116)
at
org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:191)
Comment 1 Matt Chapman CLA 2005-06-07 06:28:01 EDT
Passing over to AspectJ
Comment 2 Andrew Clement CLA 2005-06-08 04:32:41 EDT
try and look at for M3 - might be tricky as its inc compile related.  Hopefully
the changes to the compile loop we are looking at should enable us to resolve this.
Comment 3 Andrew Clement CLA 2005-06-15 04:00:09 EDT
M3 is fast becoming 'generics only' fixes so we can get it finished. inc
compilation will come later.
Comment 4 Andrew Clement CLA 2005-10-03 05:21:19 EDT
yuck ... all the generics changes for M3 (and type renaming) have moved this
error around a lot.  Does it still happen for you with the latest AJDT?  if so,
is there anyway you can supply me with an up to date stack trace? thanks.
Comment 5 Adrian Colyer CLA 2005-10-28 08:07:31 EDT
We believe these issues are fixed, but since we can't reproduce please reopen if you encounter this again 
with the latest builds.

Thanks, Adrian.
Comment 6 Barry Kaplan CLA 2005-10-28 09:41:40 EDT
Thanks, I'll keep an eye out.