You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other extensions you installed (and if the issue persists after disabling them): N/A
If using SSH remote, specify OS of remote machine:
A clear and concise description of what the bug is, including information about the workspace (i.e. is the workspace a single project or multiple projects, size of the project, etc).
After updating VS code to version 1.64.2 and updating C/C++ extension to v1.8.4, IntelliSense no longer checks the code.
Steps to reproduce
Install update
Opened VS code and got "Couldn't start client cpptools" error message
Notice that IntelliSense is not working
Expected behavior
IntelliSense works as normal.
Code sample and logs
[Error - 8:45:09 PM] Starting client failed
Launching server using command /home/cit595/.vscode-server/extensions/ms-vscode.cpptools-1.8.4/bin/cpptools failed.
The text was updated successfully, but these errors were encountered:
Hi @bonniewt . Could you try deleting the /home/cit595/.vscode-server/extensions/ms-vscode.cpptools-1.8.4 folder and installing the C/C++ extension again? That might solve the issue, if due to the wrong version of the (native binaries for the) extension being deployed to your machine. (i.e. microsoft/vscode#141696 ).
If that does not address the issue, could you enable "C_Cpp.loggingLevel": "Debug" and provide all of the output to that C/C++ output channel leading up to the repro?
Bug type: Language Service
Describe the bug
After updating VS code to version 1.64.2 and updating C/C++ extension to v1.8.4, IntelliSense no longer checks the code.
Steps to reproduce
Expected behavior
IntelliSense works as normal.
Code sample and logs
[Error - 8:45:09 PM] Starting client failed
Launching server using command /home/cit595/.vscode-server/extensions/ms-vscode.cpptools-1.8.4/bin/cpptools failed.
The text was updated successfully, but these errors were encountered: