-
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
Slow step through code #7250
Comments
Duplicate of #7240 |
Thank you for resolving this. Just note that in my case vs code does not freeze or something. I can see call stacks being loaded one by one. It just takes roughly 0.5s per thread to do step over which adds up quite quickly. If you still think it's same issue (could be) ignore this. |
We appreciate any issues opened to help us keep track and prioritize issues. There is a known slowness with lldb-mi. However, The VSCode C++ Extension does not directly work on We build the debug adapter If memory usage is high for the You can capture and send trace files to help them investigate performance issues. Here is a tutorial on how to capture a trace file but for |
This will probably not help you explicitly but just to add as much info as possible, here is hot path for lldb-mi:
|
Type: Debugger
Stepping through code (step over, step in etc...) when debugging codebase with big amount of threads (in my case it is around 20 active threads) each step takes few seconds as it reloads all callstacks from all threads. This makes debugging painfully slow to the point that its faster to spam around debug messages and build new executable.
Describe the bug
The text was updated successfully, but these errors were encountered: