-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug step out continues #13096
Comments
I keep running into this during the Smoke-Test. Should we add a note to it? |
@chrmarti do you see the same behaviour with |
Yes, same with node2 using node 7.0.0. Previously with the old protocol and node 6.3.0. |
@chrmarti OK, then this looks like a node bug. /cc @roblourens |
Also: It seems to be related to the calling function not having any further lines of actual code after the one I stepped into. We found that stepping over at the end of the stepped into function then correctly stops on the closing } of the calling function. |
I'm seeing the same behaviour with node-inspector. |
dbaeumer.vscode-eslint-1.0.7
,eg2.tslint-0.5.39
,ms-vscode.csharp-1.4.1
,msjsdiag.debugger-for-chrome-0.5.2
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: