You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DanTup opened this issue
Apr 30, 2019
· 5 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
The Continue button no longer functions - it does not send a continueRequest. The same thing happens if you send an error response. As a workaround (since I have a debugger that can't provide a stack trace yet) I've had to provide a dummy stack frame in order for resume to work (sure, a debugger that can only pause and resume is not terribly useful, but this seems like strange behaviour from VS Code).
All it does is logs when it stops (on entry), when VS Code asks for a stack trace, and when it gets a continue request, and also returns an empty stack trace.
Run the extension, open a .md file and run it with mock debug. It'll print:
Stopped on entry!
Sending empty call stack!
Now click the Continue button and observe that it never prints "Continue was called!".
Let me know if you ahve any issues reproducing with this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
If a debug adapter can't provide any frames and returns an empty array, for ex.:
The Continue button no longer functions - it does not send a
continueRequest
. The same thing happens if you send an error response. As a workaround (since I have a debugger that can't provide a stack trace yet) I've had to provide a dummy stack frame in order for resume to work (sure, a debugger that can only pause and resume is not terribly useful, but this seems like strange behaviour from VS Code).The text was updated successfully, but these errors were encountered: