Bug 5713

Summary:	NPE when searching for references in a JAR
Product:	[Eclipse Project] JDT	Reporter:	Jean-Michel Lemieux <jean-michel_lemieux>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P1
Version:	2.0
Target Milestone:	2.0 M3
Hardware:	PC
OS:	other
Whiteboard:

Description Jean-Michel Lemieux

2001-11-09 10:18:50 EST

Selected a method in the outline view (showing a class in a referenced JAR) and 
then selected "References > Workspace". The search for references works ok for 
every method in the class except for one. The class I was browing is 
ProblemMarkerManager and the method which caused the NPE is addListener.

The following stack trace was in the log:


Log: Fri Nov 09 10:18:56 EST 2001
4 org.eclipse.jdt.ui 1 Internal Error
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
	at 
org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.getExactMethod
(BinaryTypeBinding.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.lookup.Scope.findExactMethod
(Scope.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.lookup.BlockScope.getMethod
(BlockScope.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType
(MessageSend.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType
(MessageSend.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.ast.Expression.resolve
(Expression.java(Compiled Code))
	at 
org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve
(AbstractMethodDeclaration.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolve
(MethodDeclaration.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve
(TypeDeclaration.java(Compiled Code))
	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve
(TypeDeclaration.java(Compiled Code))
	at 
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve
(CompilationUnitDeclaration.java(Compiled Code))
	at 
org.eclipse.jdt.internal.core.search.matching.PotentialMatch.locateMatchesInComp
ilationUnit(PotentialMatch.java:333)
	at 
org.eclipse.jdt.internal.core.search.matching.PotentialMatch.locateMatches
(PotentialMatch.java:154)
	at 
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches
(MatchLocator.java(Compiled Code))
	at 
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches
(MatchLocator.java:376)
	at org.eclipse.jdt.core.search.SearchEngine.search
(SearchEngine.java:340)
	at org.eclipse.jdt.core.search.SearchEngine.search
(SearchEngine.java:285)
	at org.eclipse.jdt.internal.ui.search.JavaSearchOperation.execute
(JavaSearchOperation.java:76)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run
(WorkspaceModifyOperation.java:64)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1184)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:78)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)

Comment 1 Philipe Mulet

2002-02-02 07:36:56 EST

Is this a scenario where bindings where not faulted ? I remember you did fix a 
couple of these recently.

Comment 2 Jerome Lanneluc

2002-02-11 08:00:48 EST

Could not reproduce in 20011107, or in 20020205.
Do you still have the problem? If you do, please re-open this bug, zip your 
workspace, and send it to me.