-
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
C/C++ formatter stuck as #6809 #9631
Comments
The formatting getting stuck is likely due to another system blocking the formatting operation. C_Cpp.loggingLevel is available as a user/workspace setting (not workspace folder). If cpptools is using CPU, can you attach a debugger to get a call stack for the thread that appears to be doing work? https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv |
I can't activate the debugger to check if cpptools executed correctly |
The call stacks doesn't show any formatting, but it shows IntelliSense process creation. Are you able to wait for IntelliSense to be finished updating before running the format command? It also shows it's trying to use recursive includes, so you may want to remove any paths with "**" from your include path to stop using recursive includes, which could be faster. |
@sean-mcmanus Here is my call stack (I couldn't get it with the vscode - launch.json guide so I used the lldb one): call stack
|
I used lldb to get the call stack as @lucasaf04 |
@b05902034 That only shows the 1st thread which waits on stdin. Can you get call stacks for other threads? |
This issue has been closed because it needs more information and has not had recent activity. |
Environment
Bug Summary and Steps to Reproduce
Bug Summary:
same issue as #6809
and I check that its cpptools using CPU but I can't find C_Cpp.loggingLevel in settings
Other Extensions
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: