Open Samega7Cattac opened 2 years ago
From the logs above we see the include path is in the config file and was translated correctly, so why? Screenshots:
The IntelliSense process has crashed. Are you able to provide a crash call stack and/or repro file? See https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv
Is the gtkmm folder under /usr/include/gtkmm-4.0 ?
The IntelliSense process has crashed. Are you able to provide a crash call stack and/or repro file? See https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv
Need to wait for it to happen again
Is the gtkmm folder under /usr/include/gtkmm-4.0 ?
Yes, everything is in the right place
@sean-mcmanus seems the crash was not related to the headers issue, I attached to cpptools-srv and reopened a file where I was having the issue and the intellsense didn't crash. I will let it run and see if I can create a second issue for the crash
Hmm, I'm not sure why the headers are being reported as not being found then. I'll see if anyone else on our team has any ideas.
@sean-mcmanus I opened #9022 bc of the crashes of the intellsense, it started to happen more frequently (everytime I tried to compile) and tried to attach gdb but it just exists when I hit compile and the intellsense just crashes there. Because of that I don't have much information to share on that issue
Now this is happening in more than just a project What I find weird is both are CMake projects, can that be a clue? there's any know issue with it?
You could potentially try removing the configurationProvider to see if that fixes it and if so compare the Includes logging in both cases to see what is different.
After 1 month, still no issues without the configurationProvider on the config file Comparing the after and before include logs is kinda hard in this environment but I think is all the same.
I am trying to get into C++ development on linux, and my cmake project is not finding header files from the include directory in the VSCode extension, but it compiles fine, this makes VSCode unusable... I need to use another editor.
This randomly happens only in certain files and not others
@ctigrisht Do you have the CMake Tools extension installed?
@ctigrisht Do you have the CMake Tools extension installed?
yes I do VSC installed it automatically
@ctigrisht If you run C/C++: Log Diagnostics on the repro file, then you normally should see a "Custom configurations:" section with an includePath property which will show what we're receiving from CMake Tools, which would indicate if the issue is from the CMake Tools side or our extension's side.
https://github.com/microsoft/vscode-cpptools/issues/11197
I also met the same issue
@sean-mcmanus what property do I have to set in order to import directories from cmake itself?
@ctigrisht After installing the CMake Tools extension, you can set the configurationProvider setting to "ms-vscode.cmake-tools" (and running CMake: Configure).
hi @Samega7Cattac
Do you have work it out?
I have similar question. But I use cmake-tools to build project.
When ever edit a litte in header file, it shows warning and error like below.
If I want to remove these , I should reset CMake tool extension state every time.
I have set using cmake-tools
"C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools"
hi @Samega7Cattac
Do you have work it out?
I have similar question. But I use cmake-tools to build project.
When ever edit a litte in header file, it shows warning and error like below.
If I want to remove these , I should reset CMake tool extension state every time.
I have set using cmake-tools
"C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools"
Nope not yet
Bug type: Language Service
I'm edition something on LInux that require the "lib1" headers, it keeps asking to add
"/same_path_has_MYPROJECT_INSTALL_PATH/include/lib1"
to the include path, over and over, even when"${env:MYPROJECT_INSTALL_PATH}include/lib1"
it's already there and points to the same path. This happens on random files and with random libs on this project. But when i compile the errors go away and sometimes they come back later.This issue was wrongly reported on the VSCode issues (https://github.com/microsoft/vscode/issues/144830). I think every information is there and I will add here what's missing.
Steps to reproduce
Expected behavior
Intellsense should work and find the headers in the include path
Code sample and logs
I don't know if this output are related to this specific issue.
C/C++ output:
cpptools output:
Code sample
Configurations in
c_cpp_properties.json
This is an example:Logs from running
C/C++: Log Diagnostics
from the VS Code command palette Some of the names had to be removed Seems that every line on the file is being properly translated------- Workspace parsing diagnostics ------- Number of files discovered (not excluded): 40568 Number of files parsed: 4511