Bug 14141 - NullPointerException during search
Summary: NullPointerException during search
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: Other other
: P2 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-18 13:33 EDT by Olivier Thomann CLA
Modified: 2002-04-23 10:54 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2002-04-18 13:33:12 EDT 
Using 0416, I tried to get the reference for the constructor inside BaseTypeBinding. I got this 
exception before the search completion.

Caused by: 
java.lang.NullPointerException
	at 
org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.getExactConstructor(SourceTypeBinding.java:388)
	at 
org.eclipse.jdt.internal.compiler.lookup.BlockScope.getConstructor(BlockScope.java:913)
	at 
org.eclipse.jdt.internal.compiler.ast.AllocationExpression.resolveType(AllocationExpression.java:192)
	at 
org.eclipse.jdt.internal.compiler.ast.FieldDeclaration.resolve(FieldDeclaration.java:170)
	at 
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:890)
	at 
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:930)
	at 
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:213)
	at 
org.eclipse.jdt.internal.core.search.matching.MatchingOpenable.locateMatchesInCompilationUnit(MatchingOpenable.java:299)
	at 
org.eclipse.jdt.internal.core.search.matching.MatchingOpenable.locateMatches(MatchingOpenable.java:155)
	at 
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1322)
	at 
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:591)
	at 
org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:407)
	at 
org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:353)
	at 
org.eclipse.jdt.internal.ui.search.JavaSearchOperation.execute(JavaSearchOperation.java:82)
	at 
org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:64)
	at 
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1343)
	at 
org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:78)
	at 
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:98)
Comment 1 Jerome Lanneluc CLA 2002-04-19 10:52:46 EDT 
Suspect a jit problem. Do you use IBM JDK 1.3.1?
Comment 2 Olivier Thomann CLA 2002-04-19 10:54:16 EDT 
No, I use 1.4. I have this problem only when searching for the constructor 
reference. I didn't find the problem during other searches.
Comment 3 Jerome Lanneluc CLA 2002-04-19 11:01:40 EDT 
So could you please give me your workspace (and put it in the usual place) as I 
cannot reproduce this problem in mine?
Comment 4 Olivier Thomann CLA 2002-04-19 12:53:32 EDT 
I cannot reproduce it anymore in my workspace. So there is no need to send you 
this workspace and you can close this PR as WORKSFORME.
Comment 5 Jerome Lanneluc CLA 2002-04-23 10:54:45 EDT 
Closing.