-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 formatting selection #4539
Comments
@kei2e Our language server process is crashing. Can you attach a debugger to the Microsoft.VSCode.CPP.Extension.linux and provide a callstack or give more repro details? Are you using a multi-root workspace? |
@sean-mcmanus sorry, I am very new to this. Can you plz give me some instructions on how to attach a debugger to Microsoft.VSCode.CPP.Extension.linux? No, I am not using a multi-root workspace. |
There are some docs at https://code.visualstudio.com/docs/cpp/cpp-debug. You basically just need to create a launch.json file with a "(gdb) attach" config and set the program to the full path of the Microsoft.VSCode.CPP.Extension.linux binary (e.g. |
Also, we have no known crashes involving formatting, so anything special about your environment or format settings you could think of could help (might be related to Ubuntu 19). |
Also, if you could set the C_Cpp.clang_format_path to another clang-format such as from http://releases.llvm.org/download.html , it's possible that could fix/workaround the issue. |
Looks like other users have hit this at #3559 . |
@sean-mcmanus thanks for the instructions and help!
|
Okay .. it was fixed by installing clang-format, I still do not know what exactly is going on. But let me know if I can be of any help figuring that out. |
Our Insiders release should fix this clang-format issue: https://github.com/microsoft/vscode-cpptools/releases/tag/0.27.0-insiders |
Any solutions to this yet?
I have a similar issue: VSCode on Ubuntu 19.1, with C/C++ 0.26.1 extension installed. When I try to format a selected part of my code, I receive the error:
Originally posted by @kei2e in #1975 (comment)
The text was updated successfully, but these errors were encountered: