-
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
Debugger Step Over into skipFiles #118282
Comments
This is happening to me as well with nodejs backend with typescript. |
I have a breakpoint that is hit on the call site of an async function, and even though I have all js files added as skipped in launch.json file, when I press F11, debugger goes into the js file - I expect it to jump to line 9 in ts file. here is the repro https://github.com/sinapis/vscode-118282 |
Thank you for the good issue and repro steps! Turn out this bit of functionality never worked as it was intended. This'll be fixed in the nightly build. |
I press F11 and go into the promise helper in index.js, seems like both smartStep and skipFiles should avoid that |
@roblourens can you share steps? I don't repro this https://memes.peet.io/img/21-04-ed599b74-21dd-48ae-8928-dbb50e256b9d.mp4 |
I was using the https://github.com/sinapis/vscode-118282 test repo, not the OP |
That was actually a separate issue that affected attach without an |
VS Code Version:
Version: 1.54.1 (user setup)
Commit: f30a9b7
Date: 2021-03-04T22:38:31.419Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.18363
OS Version:
win10 1909
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
launch.json setting (both 2 settings are not working)
set breakpoint
Start debuggining by click the below panel
7.Stop at breakpoint
On the right, we see those files are indeed skipped in the call stack? But the Step Over still stop inside the file.
--
I apologize for my mistake if this is more about Angular specific not Vscode, but I think maybe Vscode debugger shall work as well?
The text was updated successfully, but these errors were encountered: