Bug 96306 - 3.1M7 NullPointerException while doing java search
Summary: 3.1M7 NullPointerException while doing java search
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 98051 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-05-23 11:01 EDT by Edoardo Comar CLA
Modified: 2006-03-27 06:58 EST (History)
2 users (show)

See Also:


Attachments
outline of the class (163.30 KB, image/png)
2005-05-24 04:47 EDT, Edoardo Comar CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Edoardo Comar CLA 2005-05-23 11:01:44 EDT
I get this exception either when performing a caller hierarchy or when
performing a workspace reference search.
result is: I can't find what I am searching for ;)

Error 2005-05-23 15:49:09.776 An internal error occurred during: "Java Search".
java.lang.NullPointerException
at
org.eclipse.jdt.internal.compiler.lookup.MethodBinding.signature(MethodBinding.java:655)
at
org.eclipse.jdt.internal.compiler.lookup.MethodBinding.computeUniqueKey(MethodBinding.java:308)
at
org.eclipse.jdt.internal.compiler.lookup.MethodBinding.computeUniqueKey(MethodBinding.java:296)
at
org.eclipse.jdt.internal.compiler.lookup.Binding.computeUniqueKey(Binding.java:45)
at org.eclipse.jdt.internal.core.BinaryMethod.resolved(BinaryMethod.java:328)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.newMethodReferenceMatch(MatchLocator.java:1303)
at
org.eclipse.jdt.internal.core.search.matching.MethodLocator.matchReportReference(MethodLocator.java:235)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.reportMatching(MatchLocator.java:1783)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.reportMatching(MatchLocator.java:2112)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.reportMatching(MatchLocator.java:1917)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.process(MatchLocator.java:1397)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:924)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:965)
at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1067)
at
org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(JavaSearchParticipant.java:94)
at
org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:208)
at
org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:421)
at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:532)
at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:135)
at
org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:93)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)

the source code is a very heavily overloaded static method used all over in our
plugins ....
Comment 1 Darin Swanson CLA 2005-05-23 21:38:33 EDT
Occurred on N20050523.
Comment 2 Jerome Lanneluc CLA 2005-05-24 02:05:35 EDT
Steps to reproduce this problem would be most welcome.
Comment 3 Edoardo Comar CLA 2005-05-24 04:46:42 EDT
Jerome, there are no particular steps.
I just performed a call hierarchy serach and since it failed a java search for
reference in the workspace.
in both cases with the cursor over a method in one of my plugins.
I can't send our entire workspace unfortunately.

I even restarted eclipse and rebuilt from clean - same result.
I then ran M6 and the serach completed successfully.

FYI here is a screenshot of the outline of the class the searched method is
highlighted
Comment 4 Edoardo Comar CLA 2005-05-24 04:47:10 EDT
Created attachment 21616 [details]
outline of the class
Comment 5 Jerome Lanneluc CLA 2005-06-02 10:01:09 EDT
*** Bug 98051 has been marked as a duplicate of this bug. ***
Comment 6 Jerome Lanneluc CLA 2005-06-13 05:23:05 EDT
Still cannot reproduce. Please reopen if you have steps to reproduce with 3.1 RC2.
Comment 7 Philipe Mulet CLA 2006-03-27 06:58:10 EST
reopening to close properly.
Comment 8 Philipe Mulet CLA 2006-03-27 06:58:40 EST
closing since didn't hear back in a long time.