From 89677a612e43725862c4b65c6e384c01a9cfefbc Mon Sep 17 00:00:00 2001 From: Jonah Graham Date: Fri, 7 Oct 2022 10:39:32 -0400 Subject: [PATCH] Add some links for CDT indexer FAQ --- FAQ/Indexer.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/FAQ/Indexer.md b/FAQ/Indexer.md index 81515226a5c..ce59d09594a 100644 --- a/FAQ/Indexer.md +++ b/FAQ/Indexer.md @@ -104,5 +104,6 @@ See [Setup for CDT Development](https://github.com/eclipse-cdt/cdt/blob/main/CON #### Classes of interest -- org.eclipse.cdt.internal.core.dom.parser.ProblemBinding: When you have a "Symbol 'foo' could not be resolved" error, put a breakpoint in the constructors of this class and you can work your way back in the stack where/why the parsing produced this.- org.eclipse.cdt.internal.core.parser.scanner.CPreprocessor.executeInclude: This method is where the CDT preprocessor handles \#include. - This can be a useful starting point if you want to debug why a header is not resolved or the wrong one is included or skipped, etc. +- [org.eclipse.cdt.internal.core.dom.parser.ProblemBinding](https://github.com/eclipse-cdt/cdt/blob/main/core/org.eclipse.cdt.core/parser/org/eclipse/cdt/internal/core/dom/parser/ProblemBinding.java): When you have a "Symbol 'foo' could not be resolved" error, put a breakpoint in the constructors of this class and you can work your way back in the stack where/why the parsing produced this. +- [org.eclipse.cdt.internal.core.parser.scanner.CPreprocessor](https://github.com/eclipse-cdt/cdt/blob/main/core/org.eclipse.cdt.core/parser/org/eclipse/cdt/internal/core/parser/scanner/CPreprocessor.java).executeInclude: This method is where the CDT preprocessor handles \#include. +This can be a useful starting point if you want to debug why a header is not resolved or the wrong one is included or skipped, etc.