Bug 128877 - [search] reports inexistent IMethod for binary constructor of inner class
Summary: [search] reports inexistent IMethod for binary constructor of inner class
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-21 15:09 EST by Markus Keller CLA
Modified: 2006-03-28 11:03 EST (History)
0 users

See Also:


Attachments
Patch to fix this issue (12.24 KB, patch)
2006-02-27 06:45 EST, Frederic Fusier CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2006-02-21 15:09:24 EST
I20060217-1115

- import org.eclipse.core.resources as binary plugin
- search for references to org.eclipse.core.runtime.jobs.Job.setRule(..)
- there's a match in the constructor of org.eclipse.core.internal.resources.ContentDescriptionManager$FlushJob, but the match's enclosing element does not exist.

Probably a problem with the constructor's synthetic parameter.
Maybe related to bug 47354 and bug 122880.
Comment 1 Frederic Fusier CLA 2006-02-23 08:56:58 EST
This is not related with bug 47354, bug 119249 or bug 122880.
This a problem with a change while fixing null ref warning in createHandle method of MatchLocator...:-(
Comment 2 Frederic Fusier CLA 2006-02-27 06:45:16 EST
Created attachment 35401 [details]
Patch to fix this issue

When enclosing element has no parameter, synthetic parameter type of innner class was not well computed and so its handle was not valid...
Comment 3 Frederic Fusier CLA 2006-02-27 07:47:19 EST
Released in HEAD.

Test case added in JavaSearchBugsTests
Comment 4 Olivier Thomann CLA 2006-03-28 11:03:05 EST
Clicking on FlushJob doesn't open the constructor. The location of the constructor doesn't work when the constructor has synthetic parameters.
But this seems to be related to bug 122880.
Verified using I20060328-0010 for 3.2M6.