microsoft / microsoft/vscode-cmake-tools

C++ Intellisense broken in some files, but working in other files

Open
#3,718 16 comments 1 reaction 0 assignees View on GitHub
bug Feature: cpptools integration
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Brief Issue Summary

When setting this extension as a configuration provider, Intellisense breaks in specific files, but works fine in other files.

### CMake Tools Diagnostics

```shell
-------- Diagnostics - 4/23/2024, 11:43:16 AM
Version: 1.19.9
Current Configuration:
{
"name": "Win32",
"includePath": [
"f:/Code/MNComputers/emulator/**"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.22621.0",
"compilerPath": "cl.exe",
"cStandard": "c17",
"cppStandard": "c++17",
"intelliSenseMode": "windows-msvc-x64",
"compilerPathInCppPropertiesJson": "cl.exe",
"intelliSenseModeIsExplicit": false,
"cStandardIsExplicit": false,
"cppStandardIsExplicit": false,
"mergeConfigurations": false,
"compilerPathIsExplicit": false,
"configurationProvider": "ms-vscode.cmake-tools",
"browse": {
"path": [
"f:/Code/MNComputers/emulator/**",
"${workspaceFolder}"
],
"limitSymbolsToIncludedHeaders": true
}
}
Custom browse configuration:
{
"browsePath": [
"c:/program files (x86)/sockpp/include",
"f:/code/mncomputers/emulator"
],
"compilerPath": "c:/program files/microsoft visual studio/2022/community/vc/tools/msvc/14.39.33519/bin/hostx86/x64/cl.exe",
"compilerArgs": [],
"compilerFragments": [
"/DWIN32 /D_WINDOWS /W3 /GR /EHsc /MDd /Zi /Ob0 /Od /RTC1",
"/ZI",
"/DEBUG:FULL"
]
}
cpptools version (native): 1.19.9.0
Translation Unit Mappings:
[ F:\Code\MNComputers\emulator\emulator.cpp - source TU]:
Translation Unit Configurations:
[ F:\Code\MNComputers\emulator\emulator.cpp ]:
Process ID: 25216
Memory Usage: 39 MB
Compiler Path: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\Hostx86\x64\cl.exe
Includes:
C:\Program Files (x86)\sockpp\include
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\atlmfc\include
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\um
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\ucrt
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\shared
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\winrt
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\cppwinrt
Defines:
WIN32
_WINDOWS
EBUG:FULL
Standard Version: ms_c++17
IntelliSense Mode: windows-msvc-x64
Other Flags:
--rtti
Total Memory Usage: 39 MB

------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 5112
```

### Debug Log

_No response_

### Additional Information

https://github.com/microsoft/vscode-cmake-tools/assets/57674559/0fde08db-f8b2-4177-aefc-ed39837f971c

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the configuration-provider behavior using the supplied CMake Tools Diagnostics for emulator.cpp and compare files where IntelliSense works with those where it fails. Inspect the reported compiler fragments, defines, include paths, and translation-unit configuration. Done means identifying the cause and confirming consistent IntelliSense behavior across the affected files.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp, vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.