[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] How can I troubleshoot the CDT discovery mechanism?
|
To see what files are actually indexed you can tracing the CDT indexer:
* use command line option -debug <options-file>
* put the following in the options file:
# turns on tracing for the cdt-core plugin
org.eclipse.cdt.core/debug=true
# Reports statistics for indexer
org.eclipse.cdt.core/debug/indexer/statistics=true
# Reports when and which files get indexed
org.eclipse.cdt.core/debug/indexer/activity=true
# Reports problems for indexer
org.eclipse.cdt.core/debug/indexer/problems=false
Markus.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Fredrik Attebrant
> Sent: Dienstag, 21. August 2007 14:29
> To: CDT General developers list.
> Subject: [cdt-dev] How can I troubleshoot the CDT discovery mechanism?
> Importance: Low
>
> Hi all,
>
> Trying to get the wonderfully improved CDT4 configured for a customer.
> However there are some problems with getting the discovery
> mechanism for
> a CDT Makefile project working properly.
>
> I'd like to be able to troubleshoot this and thus I wonder if there's
> some way of enabling tracing (debug printout etc) of the discovery
> mechanism?
>
> First problem is that it doesn't handle the parsing build output and
> thus fails in discovering the include paths.
>
> Next, is there a way of dumping the content of the PDOM?
> It would be good to be able to see to what extent the index
> is updated etc.
>
> Thanks!
> --Fredrik
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
