Bug 89640 - Random (?) NPE in 0325 build
Summary: Random (?) NPE in 0325 build
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.5.0M2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-30 13:46 EST by Nicholas Lesiecki CLA
Modified: 2007-02-14 05:59 EST (History)
2 users (show)

See Also:


Attachments
updated ajdtui.jar (999.96 KB, application/octet-stream)
2005-03-31 11:44 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 Nicholas Lesiecki CLA 2005-03-30 13:46:52 EST
This bug is either similar or identical to 86051. This time, there's no stack
trace either in the error log or in the message, so it's really hard to give any
more details.

I'm using build: 1.2.0.20050325175227
Comment 1 Matt Chapman CLA 2005-03-30 14:24:35 EST
Hi Nick,
We're fairly sure the other bug is fixed, so this is probably a different problem.
I assume you get the error dialog again? And I take it there is nothing useful
in the problems view either?

Matthew, this might be the same as the one you hit earlier, although of course
without a stack trace for either, it's hard to tell!

We need to find the place where our FFDC aspect is not doing its thing!!
Comment 2 Nicholas Lesiecki CLA 2005-03-30 14:52:06 EST
> I assume you get the error dialog again?

Yes

>And I take it there is nothing useful in the problems view either?

Nope

Cheers, nick
Comment 3 Matt Chapman CLA 2005-03-30 17:37:27 EST
Thanks Nick.
I think I've found the case where an exception thrown down in AspectJ doesn't
get written to the eclipse log (only the error dialog is shown). Our FFDC aspect
unfortunately isn't woven into the compiler itself!!

I've added the appropriate log() call, and will upload a new dev build tomorrow,
so we will then hopefully get to see what the real problem is!
Comment 4 Matt Chapman CLA 2005-03-31 11:44:47 EST
Created attachment 19413 [details]
updated ajdtui.jar

Nick, we're having problems uploading a build. If you have chance before that
is resolved, you could try the attached updated jar file for the
org.eclipse.ajdt.ui plugin.
Comment 5 Matt Chapman CLA 2005-04-01 03:36:21 EST
The build has now been uploaded: ajdt_1.2.0.20050331181000
Comment 6 Nicholas Lesiecki CLA 2005-04-07 13:31:55 EDT
Nick: ho hum, trying new April 7 build
Bug: _I STILL LIVE_
Nick: AAAAH! (downgrading)

:)
Comment 7 Matt Chapman CLA 2005-04-07 14:49:40 EDT
Nick, I'm fairly sure that if the bug still occurs you should now at least get a
stack trace in your .log. Please can you check. If not, please can you enter the
exact title and exact text of this error rogue dialog. Thanks.
Comment 8 Nicholas Lesiecki CLA 2005-04-08 17:20:49 EDT
Ah, you are correct, this time I have a stack trace:

(April 7 build integrated for Eclipse 3.0.1)

!ENTRY org.eclipse.ajdt.ui 4 0 Apr 08, 2005 14:16:17.572
!MESSAGE NullPointerException thrown: null
!STACK 0
java.lang.NullPointerException
	at org.aspectj.apache.bcel.classfile.JavaClass.getAllInterfaces(JavaClass.java:862)
	at org.aspectj.apache.bcel.classfile.JavaClass.implementationOf(JavaClass.java:775)
	at org.aspectj.apache.bcel.Repository.implementationOf(Repository.java:224)
	at org.aspectj.apache.bcel.Repository.implementationOf(Repository.java:231)
	at
org.aspectj.apache.bcel.generic.ReferenceType.isAssignmentCompatibleWith(ReferenceType.java:128)
	at org.aspectj.weaver.bcel.Utility.createConversion(Utility.java:387)
	at org.aspectj.weaver.bcel.BcelRenderer.renderExpr(BcelRenderer.java:78)
	at org.aspectj.weaver.bcel.BcelRenderer.visit(BcelRenderer.java:237)
	at org.aspectj.weaver.ast.Call.accept(Call.java:30)
	at org.aspectj.weaver.bcel.BcelRenderer.recur(BcelRenderer.java:148)
	at org.aspectj.weaver.bcel.BcelRenderer.visit(BcelRenderer.java:157)
	at org.aspectj.weaver.ast.And.accept(And.java:27)
	at org.aspectj.weaver.bcel.BcelRenderer.recur(BcelRenderer.java:148)
	at org.aspectj.weaver.bcel.BcelRenderer.renderTest(BcelRenderer.java:114)
	at org.aspectj.weaver.bcel.BcelAdvice.getTestInstructions(BcelAdvice.java:358)
	at org.aspectj.weaver.bcel.BcelShadow.weaveAroundClosure(BcelShadow.java:2293)
	at org.aspectj.weaver.bcel.BcelAdvice.implementOn(BcelAdvice.java:152)
	at org.aspectj.weaver.Shadow.implementMungers(Shadow.java:471)
	at org.aspectj.weaver.Shadow.implement(Shadow.java:350)
	at org.aspectj.weaver.bcel.BcelClassWeaver.implement(BcelClassWeaver.java:1618)
	at org.aspectj.weaver.bcel.BcelClassWeaver.weave(BcelClassWeaver.java:386)
	at org.aspectj.weaver.bcel.BcelClassWeaver.weave(BcelClassWeaver.java:92)
	at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1267)
	at org.aspectj.weaver.bcel.BcelWeaver.weaveWithoutDump(BcelWeaver.java:1232)
	at org.aspectj.weaver.bcel.BcelWeaver.weaveAndNotify(BcelWeaver.java:1026)
	at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:915)
	at
org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.weave(AjCompilerAdapter.java:244)
	at
org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.afterCompiling(AjCompilerAdapter.java:119)
	at
org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:385)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:683)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:191)
	at
org.aspectj.ajdt.internal.core.builder.AjBuildManager.incrementalBuild(AjBuildManager.java:109)
	at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:117)
	at
org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:165)
Comment 9 Matt Chapman CLA 2005-04-09 05:25:51 EDT
Thanks Nick, that's good progress.
I know how much Andy likes BCEL bugs so I'm passing it over :)
Comment 10 Andrew Clement CLA 2005-04-11 05:44:26 EDT
That NPE comes out because of an earlier failure trying to locate an interface
which results in a ClassNotFoundException.  BCEL (unfortunately) swallows the
CNFE, the only bit of diagnostic material coming out being a line to system.err
detailing what couldn't be found.  Sorry to ask you this Nick, but can you try
recreating but starting your Eclipse with the '-console' option as that may
cause the message to system.err to come out in a separate window.  I'm loathed
to hack fix this NPE as it will then be hiding the underlying problem entirely.