Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

an issue with the tracking header file #12704

Open
huye opened this issue Sep 12, 2024 · 3 comments
Open

an issue with the tracking header file #12704

huye opened this issue Sep 12, 2024 · 3 comments
Assignees
Labels
Feature: Configuration An issue related to configuring the extension or IntelliSense Language Service more info needed The issue report is not actionable in its current state regression A bug that didn't exist in a previous release

Comments

@huye
Copy link

huye commented Sep 12, 2024

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
Copy link
Author

huye commented Sep 12, 2024

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
Copy link
Collaborator

sean-mcmanus commented Sep 12, 2024

@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.

@sean-mcmanus sean-mcmanus self-assigned this Sep 12, 2024
@sean-mcmanus sean-mcmanus added Language Service more info needed The issue report is not actionable in its current state regression A bug that didn't exist in a previous release Feature: Configuration An issue related to configuring the extension or IntelliSense labels Sep 12, 2024
@huye
Copy link
Author

huye commented Sep 14, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Configuration An issue related to configuring the extension or IntelliSense Language Service more info needed The issue report is not actionable in its current state regression A bug that didn't exist in a previous release
Projects
Status: No status
Development

No branches or pull requests

2 participants