IntelliSense misses gcc-style precompiled headers with `compile_commands.json`

未關閉
#14,871 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
56/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript
領域
devtools

研究方向

Start by tracing how vscode-cpptools reads compile_commands.json entries for C++ source files and handles GCC's -include and -fpch-preprocess flags; compare that path with the entry producing proj.p/cpp_pch.h.gch. Use the provided commands to reproduce the missing PCH contents in src/main.cpp. Done means IntelliSense recognizes the source header used to produce the .gch and no longer reports its declarations as missing.

由索引模型根據 Issue 內容生成。

描述

Environment
  • OS and Version:
    Windows 10 19045.7807 22H2

  • VS Code Version:
    1.146.0

  • C/C++ Extension Version:
    1.35.6

  • If using SSH remote, specify OS of remote machine:
    Debian 13.7 arm64

Bug Summary and Steps to Reproduce

Bug Summary:

When providing a compile_commands.json to vscode-cpptools, IntelliSense can miss including precompiled headers depending on how they're provided.

Steps to reproduce:

Assuming a setup such as this:

├── build
│   ├── compile_commands.json
│   └── proj.p
│       ├── cpp_pch.h.gch
└── src
    ├── main.cpp
    └── pch
        └── cpp_pch.h

My build first creates a precompiled header from src/pch/cpp_pch.h, outputting it as build/proj.p/cpp_pch.h.gch. Then, when compiling main, I include it by specifying the proj.p directory as an include directory, and including it with -include cpp_pch.h. Since G++ will automatically look for <pch name>.gch, it finds and uses the already generated one. As src/pch/ is not on the include path, it never tries to include src/pch/cpp_pch.h

This produces a compile_commands.json like so:

[
  {
    "directory": "/home/user/proj/build",
    "command": "g++ -Iproj.p -I. -I.. -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O0 -g -x c++-header -MD -MQ proj.p/cpp_pch.h.gch -MF proj.p/cpp_pch.h.gch.d -o proj.p/cpp_pch.h.gch -c ../src/pch/cpp_pch.h",
    "file": "../src/pch/cpp_pch.h",
    "output": "proj.p/cpp_pch.h.gch"
  },
  {
    "directory": "/home/user/proj/build",
    "command": "g++ -Iproj.p -I. -I.. -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -fpch-preprocess -include cpp_pch.h -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O0 -g -MD -MQ proj.p/src_main.cpp.o -MF proj.p/src_main.cpp.o.d -o proj.p/src_main.cpp.o -c ../src/main.cpp",
    "file": "../src/main.cpp",
    "output": "proj.p/src_main.cpp.o"
  }
]

This works fine for compiling and linking, but IntelliSense does not properly notice that the file used as input to generate the cpp_pch.h.gch is what is actually being included via the -include cpp_pch.h. Things that are used in main.cpp get red problem squiggles, because IntelliSense doesn't know anything about what's in cpp_pch.h

Expected behavior:

Ideally vscode-cpp would notice the compile command that generates a *.gch and include the header referenced as an include for sources, especially when the IntelliSense mode is *-gcc-*

Configuration and Logs
## C/C++: Log Diagnostics


-------- Diagnostics - 13/11/2026, 15:26:57
Version: 1.35.6
Current Configuration:
{
    "name": "Linux",
    "includePath": [
        "/home/user/proj/**"
    ],
    "defines": [],
    "cStandard": "gnu17",
    "cppStandard": "gnu++17",
    "intelliSenseMode": "linux-gcc-arm64",
    "compileCommands": [
        "/home/user/proj/build/compile_commands.json"
    ],
    "intelliSenseModeIsExplicit": false,
    "cStandardIsExplicit": false,
    "cppStandardIsExplicit": false,
    "mergeConfigurations": false,
    "recursiveIncludes": {},
    "recursiveIncludesPriorityIsExplicit": false,
    "recursiveIncludesOrderIsExplicit": false,
    "compilerPathIsExplicit": false,
    "configurationProvider": "mesonbuild.mesonbuild",
    "browse": {
        "limitSymbolsToIncludedHeaders": true
    }
}
Modified Settings:
{
    "C_Cpp.default.compileCommands": "/home/user/proj/build/compile_commands.json",
    "C_Cpp.default.configurationProvider": "mesonbuild.mesonbuild"
}
Additional Tracked Settings:
{
    "editorTabSize": 4,
    "editorInsertSpaces": false,
    "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"
}
Custom browse configuration: 
{
    "browsePath": [
        ""
    ],
    "compilerPath": "g++",
    "compilerArgs": []
}
cpptools version (native): 1.35.5.0
Current database path: /home/user/.cache/vscode-cpptools/d6c28b94876ca376959235a45cf94837/.browse.VC.db
Translation Unit Mappings:
[ /home/user/proj/src/main.cpp - source TU]:
[ /home/user/proj/src/pch/cpp_pch.h - source TU]:
Translation Unit Configurations:
[ /home/user/proj/src/main.cpp ]
    Process ID: 3242704
    Memory Usage: 22 MB
    Compiler Path: /usr/bin/g++
    Language: C++
    Include Paths:
        include: /home/user/proj/build/proj.p
        include: /home/user/proj/build
        include: /home/user/proj
        system include: /usr/include/c++/14
        system include: /usr/include/aarch64-linux-gnu/c++/14
        system include: /usr/include/c++/14/backward
        system include: /usr/lib/gcc/aarch64-linux-gnu/14/include
        system include: /usr/local/include
        system include: /usr/include/aarch64-linux-gnu
        system include: /usr/include
    Defines:
        _GLIBCXX_ASSERTIONS=1
        _FILE_OFFSET_BITS=64
    Standard Version: c++17
    IntelliSense Mode: linux-gcc-arm64
    Other Flags:
        --g++
        --gnu_version=140200
    compile_commands.json entry:
        directory: /home/user/proj/build
        file: /home/user/proj/src/main.cpp
        command: g++ -Iproj.p -I. -I.. -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -fpch-preprocess -include cpp_pch.h -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O0 -g -MD -MQ proj.p/src_main.cpp.o -MF proj.p/src_main.cpp.o.d -o proj.p/src_main.cpp.o -c ../src/main.cpp
        output: proj.p/src_main.cpp.o
[ /home/user/proj/src/pch/cpp_pch.h ]
    Process ID: 3242926
    Memory Usage: 21 MB
    Compiler Path: /usr/bin/g++
    Language: C++
    Include Paths:
        include: /home/user/proj/build/proj.p
        include: /home/user/proj/build
        include: /home/user/proj
        system include: /usr/include/c++/14
        system include: /usr/include/aarch64-linux-gnu/c++/14
        system include: /usr/include/c++/14/backward
        system include: /usr/lib/gcc/aarch64-linux-gnu/14/include
        system include: /usr/local/include
        system include: /usr/include/aarch64-linux-gnu
        system include: /usr/include
    Defines:
        _GLIBCXX_ASSERTIONS=1
        _FILE_OFFSET_BITS=64
    Standard Version: c++17
    IntelliSense Mode: linux-gcc-arm64
    Other Flags:
        --g++
        --gnu_version=140200
    compile_commands.json entry:
        directory: /home/user/proj/build
        file: /home/user/proj/src/pch/cpp_pch.h
        command: g++ -Iproj.p -I. -I.. -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O0 -g -x c++-header -MD -MQ proj.p/cpp_pch.h.gch -MF proj.p/cpp_pch.h.gch.d -o proj.p/cpp_pch.h.gch -c ../src/pch/cpp_pch.h
        output: proj.p/cpp_pch.h.gch
Total Memory Usage: 43 MB
Browse Paths from compile_commands.json, from workspace folder: /home/user/proj
    /home/user/proj
    /usr/include
    /usr/lib/gcc/aarch64-linux-gnu/14/include
    /usr/local/include
Other Extensions
Additional context

I'm using Meson as a build system which does exactly this for how it handles PCHs, but the issue could happen with any build system, or even just providing the compile commands manually.

Related topics I found while figuring this out, as I had assumed it was a meson (or their extension) thing before realizing the PCH info was actually making it into compile_commands.json: https://github.com/mesonbuild/meson/issues/10590, https://github.com/mesonbuild/vscode-meson/issues/238

主要語言
TypeScript
星號
6.2k
分支
1.7k
平均合併
1 天 17 小時
30 天內合併 PR
12

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

microsoft/vscode-cpptools 的其他 Issue

查看 microsoft/vscode-cpptools 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。