Closed EmbeddedBacon closed 1 year ago
Can you attach a debugger to cpptools, break into the debugger, and provide the call stack that appears to have tag parsing work on it? It could be related to the "fixed" bug https://github.com/microsoft/vscode-cpptools/issues/9076 (i.e. the fix there might not be good enough in your case).
The workaround is to add the file's folder to the C_Cpp.files.exclude (or the file itself, if you change the C_Cpp.exclusionPolicy to run on files).
And this is a 1.16.x regression?
@sean-mcmanus , I think I found part of my problem. In the project there are settings for the extension in .vscode/c_cpp_properties.json and .vscode/settings.json. I had been placing settings in the .vscode/c_cpp_properties.json, but without me knowing others had place settings in the .vscode/settings.json. They are mostly the same, but some differences. I updated these settings so everything is in the .vscode/c_cpp_properties.json. Seems tag parsing and intellisense works better now.
I do have a question, if the standard convention to place settings in .vscode/settings.json or .vscode/c_cpp_properties.json for the c/c++ extension?
It depends on the setting and how your code is organized, so we haven't made any convention recommendations here. There's not a lot of overlap between those two configuration files. We have C_Cpp.default.*
settings which sets defaults for anything that's not set explicitly in c_cpp_properties.json
(and allows for configuration of source files when c_cpp_properties.json
is not available because there are no folders open in the workspace).
So if all your configurations require the same default values, you can use the C_Cpp.default.*
settings so that you don't have to set the same values repeatedly in your c_cpp_properties.json
configurations.
Environment
In my current project the tag parsing appears to have stalled. During the tag parsing the process stalls at a large hardware generated header file which is about 223 MB in size. There are 2,552 files with a total size of 556MB of all files. Issue is also referenced in #11003.
Bug Summary and Steps to Reproduce
Bug Summary:
Steps to reproduce:
Expected behavior:
Configuration and Logs
Other Extensions
No response
Additional context
No response