-
Notifications
You must be signed in to change notification settings - Fork 118
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
Crash after updating to 0.1.32. #734
Comments
cc @JVApen Does the crash happen on clangd startup (i.e. as soon as you open a C/C++ source file), or in response to something specific? Do you have any settings in VSCode user or workspace settings starting with |
No, I use code-server rather than VSCode. It's a pretty new environment. No settings changed with |
Hi. I'm having the exact same issue. The extension suddenly started failing to start clangd without any changes to settings or files. This happens on both WSL and Windows, and it happens on startup. When opening a file in Windows, the error message is different:
I can copy-paste the exact same path to powershell and clangd will start successfully. EDIT: I use VSCode. |
Hi. I'm having the exact same issue with 0.1.32 too. Downgrade to 0.1.31 works fine. I use VSCode in devcontainer.
|
@HighCommander4 I don't understand, I've extensively tested this (on Linux, as I cannot build it on Windows). I have holidays for the next 11 days so won't be able to look into it. Can you revert once again? I'm really sorry. |
Hi. I'm having the exact same issue with 0.1.32 too. Downgrade to 0.1.31 works fine. I use vscode-server |
same issue with 0.1.32, I use vscode with remote ssh, the remote clangd is crashed when I upgrade clangd extension from 0.1.31, downgrade to 0.1.31, then everything is fine, the log is:
|
It seems like a new parameter was introduced: Not sure if the default is handled correctly. Defining it in the settings.json seems to work: |
This works for me |
Reverted the regressing change in #736 and put out version 0.1.33 which contains the revert. Apologies to everyone for the churn. We really need a way to create nightly/unstable releases for this plugin, to be able to test out changes without pushing them to the entire user population; I'll see if I can find some time to set up a CI action for that. |
Crash after updating to 0.1.32. Downgrade to 0.1.31 works fine.
Logs
System information
Clangd version (from the log, or
clangd --version
):clangd extension version: 0.1.32
Operating system: Ubuntu
The text was updated successfully, but these errors were encountered: