[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[cdt-dev] Indexer diagnostics
|
Hi,
I have made it easier to find out what the indexer does. Here a
short summary:
Indexer Diagnostics:
* After rebuilding an index, an info-line is written to the log:
Indexed 'c++-exe' (8 sources, 49 headers) in 0.91 sec:
1,909 declarations; 757 references; 2 unresolved inclusions;
0 syntax errors; 4 unresolved names (0.15%)
* In the context menu of a project you'll find an action to search for
all unresolved includes (Index - Search For Unresolved Includes)
* In the context menu of a translation-unit you'll find an action
to dump the configuration with which the file is parsed and the
errors found to a log-file (Index - Create Parser Log).
* There are more tracing options for the indexer:
the old ones:
org.eclipse.cdt.core/debug/indexer/activity
org.eclipse.cdt.core/debug/indexer/statistics
org.eclipse.cdt.core/debug/indexer/problems
the additional ones:
org.eclipse.cdt.core/debug/indexer/problems/inclusion
org.eclipse.cdt.core/debug/indexer/problems/scanner
org.eclipse.cdt.core/debug/indexer/problems/syntax
The related bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=213561
Markus.
Attachment:
sampleParserLog.log
Description: sampleParserLog.log
Attachment:
unresolved-inclusion-search.jpg
Description: unresolved-inclusion-search.jpg