Open travelling-clouds opened 10 months ago
Thank you for submitting this issue. It looks like the extension is attempting to look inside of the system volume information
folder with an unelevated user won't have access too. As a workaround, consider opening the folder on another disk or location on your machine. Currently looking into this further.
I'm pretty sure that looking into the System Volume Information folder is unintentional. Is your workspace on the F:
drive? Does it have any symlinks in it?
Also, in all of your configurations, can you also please remove the paths to the standard headers from the includePath
setting? Just change them back to "includePath": [ "${workspaceFolder}/**" ]
. When you set a compilerPath
we discover the paths to the standard headers automatically, and adding them manually can mess up the include ordering that your program expects.
I'm pretty sure that looking into the System Volume Information folder is unintentional. Is your workspace on the
F:
drive? Does it have any symlinks in it?Also, in all of your configurations, can you also please remove the paths to the standard headers from the
includePath
setting? Just change them back to"includePath": [ "${workspaceFolder}/**" ]
. When you set acompilerPath
we discover the paths to the standard headers automatically, and adding them manually can mess up the include ordering that your program expects.
Thank you. I've done what you say. And I think that I've found out the problem.
I have 2 operation systems on my laptop, one is Windows, the other is Ubuntu Linux. So, there is a configuration for Linux. I did the tests like the video below. Notes: I did these tests after updating VS Code to the newest version 1.85.
Tests
That's strange, and the settings of "name": "Linux", includePath": [ "${workspaceFolder}/**", "/usr**" ]
was added to my configuration automatically. And I think that the configuration for Linux will not affect my operations on Windows.
Now my c_cpp_properties.json
is like this:
{
"configurations": [
{
"name": "Win32",
"includePath": [
"${workspaceFolder}/**",
"D:\\Program Files\\Microsoft Visual Studio\\IDE\\VC\\Tools\\MSVC\\**"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.22000.0",
"compilerPath": "D:/Program Files/Microsoft Visual Studio/IDE/VC/Tools/MSVC/14.34.31933/bin/Hostx64/x64/cl.exe",
"cStandard": "c17",
"cppStandard": "c++14",
"intelliSenseMode": "windows-msvc-x64"
},
{
"name": "c++",
"includePath": [
"${workspaceFolder}/**",
"D:/Program Files/GCC/mingw32/**"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.22000.0",
"compilerPath": "D:/Program Files/GCC/mingw32/bin/c++.exe",
"cStandard": "c17",
"cppStandard": "c++14",
"intelliSenseMode": "windows-gcc-x64"
},
{
"name": "g++",
"includePath": [
"${workspaceFolder}/**",
"D:/Program Files/GCC/mingw32/**"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.22000.0",
"compilerPath": "D:/Program Files/GCC/mingw32/bin/g++.exe",
"cStandard": "c17",
"cppStandard": "c++14",
"intelliSenseMode": "windows-gcc-x64"
},
{
"name": "Linux",
"includePath": [
"${workspaceFolder}/**",
"/usr/**"
],
"defines": [],
"compilerPath": "/usr/bin/gcc",
"cStandard": "c17",
"cppStandard": "c++17",
"intelliSenseMode": "linux-gcc-x64"
}
],
"version": 4
}
Environment
Bug Summary and Steps to Reproduce
Bug Summary: I can't start C/C++ language server when I update extension
C/C++
.Steps to reproduce:
C/C++
. Notes: I can use C/C++ language server before updating. The version was 1.16.3 before.Unable to start the C/C++ language server. IntelliSense features will be disabled. Error: Error: EPERM: operation not permitted, scandir 'f:/System Volume Information'
Just Like:Expected behavior: I hope to solve this problem/bug. I tried on other machines but the same problem arose.
Configuration and Logs
Other Extensions
You can see what extensions I installed in the image below. I tried to disable other extensions except C/C++, C/C++ Extension Pack, but the problem still arose.
Additional context
No response