How to Debug the Eclipse C/C++ Indexer

This page will guideline you to debug the C/C++ Indexer in Eclipse when you meet C/C++ Indexer Issues like below:
1.Eclipse takes long time to do the C/C++ Indexer after importing your C/C++ project
2.Eclipsewill get Out of Memory exception during C/C++ Indexer

Setup the debug process by below way:

1. Open the Eclipse configure file : /eclipse/eclipseRE/configuration/config.ini, add below line:

osgi.debug=/<path>/my_debug.option
1

2. Create my_debug.option in folder /path/ and add below content:

#turn on tracing for the cdt-core plugin
org.eclipse.cdt.core/debug=true
org.eclipse.cdt.core/debug/indexer=true

org.eclipse.cdt.core/debug/pdomtimings=true
org.eclipse.cdt.core/debug/parser=true
org.eclipse.cdt.core/debug/deltaprocessor=true
org.eclipse.cdt.core/debug/scanner=true
org.eclipse.cdt.core/debug/model=true

#Reorts sequence of files indexed
org.eclipse.cdt.core/debug/indexer/activity=true
# Reports statistics for indexer
org.eclipse.cdt.core/debug/indexer/statistics=true
# Reports unresolved inclusions for indexer
org.eclipse.cdt.core/debug/indexer/problems/inclusion=true
# Reports scanner-problems for indexer (other than unresolved includes)
org.eclipse.cdt.core/debug/indexer/problems/scanner=false
# Reports syntax-problems for indexer
org.eclipse.cdt.core/debug/indexer/problems/syntax=false
# Reports problems for indexer, including inclusion-, scanner-, syntax- and  resolution-problems.
org.eclipse.cdt.core/debug/indexer/problems=false
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

3. Start Eclipse and import your C/C++ project
4. Indexing log will be printed out in Console