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
The debug adapter first sends the response and then a stopped event (with reason step) after the step has completed.
The mock debug adapter appears to do this in reverse, violating the spec.
Looking at https://github.com/microsoft/vscode-mock-debug/blob/main/src/mockDebug.ts#L511-L539, it appears that the runtime step method (which indirectly, but as far as I can tell synchronously, sends the stop event) is called before sending a response to the step request.
The text was updated successfully, but these errors were encountered:
The DAP specification (https://microsoft.github.io/debug-adapter-protocol/specification#Requests_Next) states the following about all the step requests (next, stepIn, stepOut, stepBack):
The mock debug adapter appears to do this in reverse, violating the spec.
Looking at https://github.com/microsoft/vscode-mock-debug/blob/main/src/mockDebug.ts#L511-L539, it appears that the runtime step method (which indirectly, but as far as I can tell synchronously, sends the stop event) is called before sending a response to the step request.
The text was updated successfully, but these errors were encountered: