-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
UI doesn't indicate each thread listed in the call stack as having been "PAUSED ON EXCEPTION" on loading core dump #165032
Comments
Initial investigation shows that this is from
I think it essentially clears the previous pause reason when processing the Kinda related to #70107 |
@roblourens, I imagine that that's an implication of the design. Currently, LLDB supports only process-centric debugging. So, when any thread in a process stops, all the other threads are stopped too. I reckon that that's why lldb-vscode reports allThreadsStopped as true for every stopped event. However, AFAICT, lldb-vscode maintains neither a list nor the states of the processes and threads under debug, and relies on pertinent events broadcast by LLDB to report stopped events. Now, if I'm not wrong, then all the threads in a core dump are stopped. So, I'd expect LLDB to broadcast a pertinent event for each thread in a core dump, and lldb-vscode to consequently report stopped events for all the threads. |
Sure, that's fine. Seems correct for vscode to support this the way you're using it. |
@roblourens, thanks! 😁 BTW, is it too early for any work on this to be planned for a specific release? I only ask so that I can offer our customers a ballpark estimate of when they can expect the fix for this to become available. 😬 |
…ped event with allThreadsStopped=true Fix #165032
How does next month sound? 😄 |
And once the PR above is merged, and we have resumed shipping new Insiders after this week's release (should be by the end of the week, or next Monday), I'd appreciate you verifying that the issue is actually fixed |
@roblourens, sure, I'd be happy to! Thanks a lot for looking into this! 😁 |
@roblourens, the UI indicates each thread listed in the call stack as having been PAUSED ON EXCEPTION in the latest release of Visual Studio Code Insiders. |
Version of VS Code: 1.67.2
OS: Ubuntu 18.04.6 LTS
Reproducible steps that cause the issue:
Have Visual Studio Code load a core dump in lldb via lldb-vscode (debug adapter for Visual Studio Code available as part of the LLDB project, which, to the best of my knowledge, is unpublished) by employing an attach configuration akin to the following –
What I expect to see, versus what I actually see:
All threads in the process are stopped with reason exception –
So, I'd expect the UI to indicate each thread listed in the call stack as having been PAUSED ON EXCEPTION. However, I see that the UI indicates only Thread # 23 as having been PAUSED ON EXCEPTION, and others as having been PAUSED –
What's curious, though, is that if allThreadsStopped is reported as false in each of the pertinent stopped events, then the UI indicates all threads in the call stack as having been PAUSED ON EXCEPTION –
Kindly let me know in case any additional information is required.
The text was updated successfully, but these errors were encountered: