an issue with the tracking header file

[huye]

Type: Bug

After upgrading VSCode to 1.93, some types in the code appear as undefined or have type errors.

I don't know if it's because the extension was automatically updated. I have now reduced the expansion to 1.21.6 and it will be normal.

My current version is normal, the problematic version is after 1.22.

I don't know if there is a problem with the path processing of system header files.

Extension version: 1.21.6
VS Code version: Code 1.93.0 (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z)
OS version: Darwin x64 23.5.0
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	2, 3, 3
Memory (System)	16.00GB (0.33GB free)
Process Argv	--crash-reporter-id 15cc245c-aeec-42e3-ab0f-31fcac4737ed
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
945dj816:31013170
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl1:31134654
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31134774
wkspc-onlycs-t:31132770
wkspc-ranged-t:31125599
pme_test_t:31118333
ei213698:31121563

[huye]

The following are examples of errors:

note: I have correctly included the header files and can compile and run normally.

typedef uint64_t myint;
When the mouse is placed on it, it prompts:

identifier "uint64_t" is undefined

myint myvar;
Same as above:

typedef <error-type> myint

[sean-mcmanus]

@huye 1.22.x changed the behavior of the recursive includes feature that is used if "**" is at the end of an includePath, which is the default, e.g. ${workspaceFolder}/** (#11485). If your root recursive include path contains any file with the same name as a system include path then it'll be used instead of the system include path. You can run the C/C++: Log Diagnostics command after opening a source file to see the list of include paths that are generated by the "**". If you can add the include paths with system headers to C_Cpp.files.exclude then it could cause the system headers to be used instead.

[huye]

The header file settings remain the same before and after the upgrade. The system header file path is the default value.

[github-actions]

Hey @sean-mcmanus, this issue might need further attention.

@huye, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[huye]

After I updated it again, it became normal.
My current version information is as follows:

Version: 1.94.2
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin x64 23.5.0

C/C++
C/C++ IntelliSense v1.22.8