OS: Windows 10
VSCode version: v1.82.3
CodeLLDB version: v1.10.0
Compiler: rustc
Debuggee: Windows executable via "platform select remote-windows"
When I am debugging and stopped on a breakpoint, after focusing the thread and looking at variables whenever I press F11 (or similar) to step to the next line/instruction I lose focus from the thread I was debugging, therefore no longer showing me the variables until I click on the thread I was already on.
As you can imagine this makes the step functions virtually useless.
I have already found a similar problem on the discussions page here.
But since it was unanswered for more than half a year I assumed it was not some setting but instead a bug in the extension.
Instead of always focusing thread 1 for me the debugger loses focus completely, allowing me to not even debug single-threaded programs...
OS: Windows 10 VSCode version: v1.82.3 CodeLLDB version: v1.10.0 Compiler: rustc Debuggee: Windows executable via "platform select remote-windows"
When I am debugging and stopped on a breakpoint, after focusing the thread and looking at variables whenever I press F11 (or similar) to step to the next line/instruction I lose focus from the thread I was debugging, therefore no longer showing me the variables until I click on the thread I was already on.
As you can imagine this makes the step functions virtually useless.
I have already found a similar problem on the discussions page here. But since it was unanswered for more than half a year I assumed it was not some setting but instead a bug in the extension.
Instead of always focusing thread 1 for me the debugger loses focus completely, allowing me to not even debug single-threaded programs...