-
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
Language Server Crashed #11805
Comments
Are you able to attach a debugger to cpptools.exe to get a call stack? It could be a duplicate of #11781 . It looks like it might be crashing while trying to tag parse a particular file. |
How to debug it when vscode is being opened? I've attached GDB v11.2 to
|
I've corrected the targetArchetecture to "x64" but it does nothing but remove the warning |
Could you explain a bit more about the background project? We have the same issue in my company and seems that could be a workaround, at least on our scenario. I don't know what could be the impact. Check my thread #11745 c_cpp_properties.json {
"configurations": [
{
"name": "test-linux",
"includePath": [
"${default}",
"${workspaceFolder}/**",
],
"defines": [],
"cStandard": "c17",
"cppStandard": "c++14",
"intelliSenseMode": "linux-clang-x64"
}
],
"version": 4
} If you still face the same issue, try adding this to settings.json {
"cmake.loadCompileCommands": false
} |
I'm just a beginner and I just want to open the editor |
Hi @Zes-MinKey-Young . The log you posted indicated version 1.17.5 of the C/C++ extension. Are you still experiencing this issue with the latest version? We have since addressed a known crash on startup (related to trying to process malformed JSON settings values). That was fixed in 1.18.3, but I'd suggest trying the very latest insiders (currently 1.19.1, though 1.19.2 should be available soon), to rule out issues that may have already been addressed. I don't there are any remaining start-up crashes on our radar, so if you or @borjamunozf are still reproducing an issue and can help by providing us log output, system and configuration details, we would be keen to investigate further. |
@Colengms Yes, I'm still faced with this problem.
|
cpptools output is still a single line. |
Hi @Zes-MinKey-Young . Since we're not tracking an issue impacting everyone, there would seem to be something about your environment or configuration that we may need to identify to reproduce and address the issue. In your most recently log, I noticed that a crash did not occur until Was the configuration in your first message the contents of your
Could you clarify the contents of your Does this problem repro for you with a simple scenario, such as a folder with a single simple source file, and no particular configuration? Can you refer us to which of the MinGW distribution you are using, and perhaps which compiler package you've installed? |
|
@Colengms Was there more info needed still? @Zes-MinKey-Young Is there some scenario where it can be made to not crash? |
@sean-mcmanus How can I find one scenario? It is just a simple open-up and I even could not start my c++ coding :( |
any update? same problem |
Hi @shenjiangqiu . Could you open a new issue with your repro details? Since this issue is very general and not yet understood, it's possible you're seeing something with a different root cause. @Zes-MinKey-Young I don't believe we have enough information to investigate this yet. Does this repro for you on another system? Does it repro without any other extensions installed? I do see many instances of I also see that your database is indicated as being corrupted, and the crash occurs later, on the first attempt to 'tag parse' a file, which would ingest it into the database. There could be some issue with accessing your database or database path. Could you try specifying a new location for that database using the Also, could you provide updated logs from the latest version of the C/C++ extension (1.20.0 insiders)? |
@Colengms I tried to reinstall the whole operating system(from archlinux to ubuntu 22.04) and this problem consist. The log shows:
something I have tried:
Now, I doubt it might be a hardware issue. Any suggestions how to test it? maybe:
|
@shenjiangqiu What is your C_Cpp.loggingLevel set to? |
Hi @shenjiangqiu . Could you open a new issue and provide the information requested in the new issue template? There are many possible reasons a crash can occur, and it's possible your crash is not the same as encountered by the user who opened this issue. To see what's going on, it would really help to have the following information:
|
@Colengms @sean-mcmanus I have created an new issue: #12201 #12201 |
Hey @Colengms, this issue might need further attention. @Zes-MinKey-Young, you can help us out by closing this issue if the problem no longer exists, or adding more information. |
This issue has been closed because it needs more information and has not had recent activity. |
Environment
Bug Summary and Steps to Reproduce
The language server crashed every time I open VSCode
Configuration and Logs
C/C++ logging:
CPPTools logging: single line
Other Extensions
Additional context
No response
The text was updated successfully, but these errors were encountered: