Goto definition (F12) not working with (recursive) includes

Abierto
#14,868 2 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Colengms ya está trabajando en esto.

Desde el 10/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug fixed Language Service
Environment

OS: Kubuntu

VS Code

Version: 1.145.2
Commit: c4453f8ea430795f941c1b2ff6c9321135a74a02
Date: 2026-11-06T04:28:13Z
Electron: 43.8.3
ElectronBuildId: 15784459
Chromium: 150.0.7871.250
Node.js: 24.22.1
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.103.r41379698026.g3219c66
@github/copilot-sdk: 1.0.27.41379698026.g3219c66
OS: Linux x64 7.0.0-43-generic snap

CPPTools

Identifier ms-vscode.cpptools
Version 1.35.6
Bug Summary and Steps to Reproduce

Bug Summary:
Example repository: https://github.com/BobbyTables42/VsCodeIntelliSenseTest2

Steps to reproduce:

  1. Open the workspace (or reload window if already opened)
  2. Reset IntelliSense Database
  3. Open NewClass.cpp
  4. Ctrl+Click on include or click it and press F12
  5. Tooltip tells me "No definition found for NewClass"
  6. F12 onto the class name switches to NewClass.h. So he knows the file but does not remember where it was when the include is clicked.

Expected behavior:
Open NewClass.h when "#include "NewClass.h" is clicked. Include path in c_cpp_properties.json has /NewProject/**" in it so it should parse includes recursively.

Configuration and Logs
-------- Diagnostics - 10.11.2026, 15:47:56
Version: 1.35.6
Current Configuration:
{
    "name": "test config",
    "cStandard": "c11",
    "cppStandard": "c++11",
    "includePath": [
        "/mnt/daten/gitTest/VsCodeIntelliSenseTest2/NewProject/**"
    ],
    "browse": {
        "path": [
            "/mnt/daten/gitTest/VsCodeIntelliSenseTest2"
        ],
        "limitSymbolsToIncludedHeaders": true
    },
    "compilerPathIsExplicit": false,
    "cStandardIsExplicit": true,
    "cppStandardIsExplicit": true,
    "intelliSenseModeIsExplicit": false,
    "recursiveIncludesPriorityIsExplicit": false,
    "recursiveIncludesOrderIsExplicit": false,
    "intelliSenseMode": "linux-gcc-x64",
    "mergeConfigurations": false,
    "recursiveIncludes": {},
    "compilerPath": "/usr/bin/gcc"
}
Modified Settings:
{
    "C_Cpp.clang_format_sortIncludes": false,
    "C_Cpp.loggingLevel": "Debug"
}
Additional Tracked Settings:
{
    "editorTabSize": 2,
    "editorInsertSpaces": true,
    "editorAutoClosingBrackets": "languageDefined",
    "filesEncoding": "utf8",
    "filesAssociations": {},
    "filesExclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/.jj": true,
        "**/.DS_Store": true,
        "**/Thumbs.db": true
    },
    "filesAutoSaveAfterDelay": false,
    "editorInlayHintsEnabled": true,
    "editorParameterHintsEnabled": true,
    "searchExclude": {
        "**/node_modules": true,
        "**/bower_components": true,
        "**/*.code-search": true
    },
    "workbenchSettingsEditor": "ui"
}
cpptools version (native): 1.35.5.0
Current database path: /home/foo/.cache/vscode-cpptools/ba65afcebebc2556e0207e0fe7f03883/.browse.VC.db
No active translation units.
Other Extensions

No response

Additional context

No response

Lenguaje dominante
TypeScript
Estrellas
6.2k
Forks
1.7k
Merge medio
1 d 17 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-cpptools

Todos los issues de microsoft/vscode-cpptools

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.