Debug: StoppedEvents do not reflect in UI for non-active debug sessions

[mblout]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.81.1
• OS Version: any

Steps to Reproduce:

1. Run the vscode-mock-debug example, and launch TWO "Debug readme.md" debug sessions. The first one will show an expanded call stack, but after the second launch, they will both have collapsed call stacks.

2. expand the second one, so you see only threads, and use the "step" control on that thread to step. Notice that the variables do not show for the stopped thread, and the call stack does not expand to show the current frame.

This happens because it does not focus on stopped events from the adapter for sessions that are not the currently focused session in the UI.

For this mock-debug use-case, it doesn't seem terrible, since you can easily expand/select a stack frame to get it to work, because you're using the Call Stack UI for stepping

I have a use-case where I'm controlling my backend's active thread with the GDB/MI '-thread-select" command (yes, I know it's deprecated, but our GDB-like debugger requires it). I can issue commands from a terminal to change thread, but I cannot get that to reflect in the UI unless the session I am sending commands to is the active one. And there is no API for me to set the active session.

Having an API to explicitly set the active session would be useful.
But would it also make sense to set the active session when the UI receives an event from a adapter?

[mblout]

i took a quick stab at implementing a command that would allow me to work around this, since
it appears its intentional that the code skips events for non-focused session

PR: #190996

from debugSession:
// Only take focus if nothing is focused, or if the focus is already on the current session

[roblourens]

I see 1. but I don't see 2- it does expand the thread in that case. Do you still see the issue with mock-debug? If so could you do a quick screen recording so I know I'm looking at the right thing?

[roblourens]

Only take focus if nothing is focused, or if the focus is already on the current session

That still seems correct to me. The user should have control over this. If I am stepping through a session, what happens if another session steals focus and I accidentally press F10 on that session instead of the one I was trying to look at?

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!