-
Notifications
You must be signed in to change notification settings - Fork 37.4k
Closed
Labels
*caused-by-extensionIssue identified to be caused by an extensionIssue identified to be caused by an extensiondebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issues
Description
- VSCode Version: 1.16.0-insider
- OS Version: OSX 10.11.6
Steps to Reproduce:
- Start debugger session with a debugger extension that supports multiple stopped threads.
- Stop at least two threads.
- Step over with the second thread.
Reproduces without extensions: Yes
Apologies for the watermark, but you can see the UI remains focused on the first thread after the second thread stops again. I think the UI should refocus on the thread that is most recently stopped.
I suspect the issue is in debugService.tryToAutoFocusStackFrame(). I think that if-statement should be true if there is no callstack or the current focused stack frame is in the same thread as the method parameter. So, something like this:
if (!callStack.length || (this.viewModel.focusedStackFrame && this.viewModel.focusedStackFrame.thread.threadId === thread.threadId)) {
Metadata
Metadata
Assignees
Labels
*caused-by-extensionIssue identified to be caused by an extensionIssue identified to be caused by an extensiondebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issues
