Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349647 - After running C/C++ indexer, cannot find references for a function
Summary: After running C/C++ indexer, cannot find references for a function
Status: RESOLVED WORKSFORME
Alias: None
Product: CDT
Classification: Tools
Component: cdt-indexer (show other bugs)
Version: 8.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Markus Schorn CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-17 02:30 EDT by Kevin Connor Arpe CLA
Modified: 2017-01-10 02:23 EST (History)
6 users (show)

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 Kevin Connor Arpe CLA 2011-06-17 02:30:42 EDT 
Build Identifier: 20110301-1815

I have a large C/C++ project in CDT.  About 1000 header files and source files.

Right click on root -> Index -> Freshen All Files
(wait a while)

Open a source file.
Put my cursor in the name of one function.
Right click -> References -> Project

Search window says: (0 matches)

I use regular File Search for function name... I find references.

Something interesting to note:
This project is checked out using Subclipse (SVN for Eclipse).
I noticed the indexer always falls out of date after an update.
Takes a few "Refresh" or "Index -> Freshen All Files" to get things working again.

My Subclipse plug-in is 2.2.3

Reproducible: Sometimes

Steps to Reproduce:
See details above.
Comment 1 Markus CLA 2011-06-20 04:22:30 EDT 
Hello together,

the problem exists also for me. We have also a Project with approx. an equal amount of header and source files. The Indexer isn't able to find all references for functions. I use the latest version of source navigator for crossreferencing instead, but I would love to have all in one tool. 

sincerely

M
Comment 2 Markus Schorn CLA 2011-06-29 08:36:42 EDT 
Sounds similar to bug 302767. Are there any suspicious log-entries in <workspace>/.log/.metadata ?
Comment 3 Nathan Ridge CLA 2017-01-10 02:23:41 EST 
If you're still seeing this, please reopen and provide the information requested in comment 2.