Vscode: Debugger doesn't step into

[jrieken]

• open VS Code sources
• set a breakpoint in strings.test.ts, like here
• run the Unit Tests launch config
• see the breakpoint is being hit
• select step into, 🐛 execution resumes instead

[weinand]

@isidorn I cannot reproduce this. Can you?

[rebornix]

Can not reproduce on macOS.

[octref]

Can't repro. I'm on macOS too.

[isidorn]

Can not repro both on insiders and stable, macOS

[jrieken]

I am not accepting a majority vote here

[weinand]

@jrieken let me know when we can debug this at your laptop.

[jrieken]

To reproduce add these two watch expressions this._scanner.tokenText(this._token) and this._scanner.tokenText(this._prevToken) and the _first_ step into won't work

[weinand]

Any watch expression will trigger this problem.

[weinand]

Haven't found fix for this. Needs more investigation...

[edvinv]

Having the same problem. After removing all watch expression, step into starts to work. With watch expressions step into behaves like continue execution.

[lmessinger]

same here, problem still exists on ver 1.10.2. , node 6.5.0, shell 1.4.6, renderer 53.0.2785.143. if i continue with F11s, then it might return to same position. so it might be related to an asynchronous execution issue.

This used to work , and is impeding work for ppl using VSCode more than just an editor. I would give it very high priority.

[weinand]

@lmessinger could you please confirm that the problem only occurs if you have at least one watch expression.

[lmessinger]

confirmed. running for 2 days now w/out issues (at last)

[weinand]

@lmessinger now I'm confused.
So you can confirm that the problem only occurs if you have at least one watch expression and that it does not occur if you remove all watch expressions?

But what does "running for 2 days now w/out issues (at last)" then mean?

[lmessinger]

correct for the first paragraph.

For second, what I meant is that i removed it two days ago and have been developing for the last 2 days, and all works well.

[edvinv]

I can also confirm that after adding single watch expression Step into (F11) behaves like Continue (F5).
So I'm not using watch expressions at all, because I lose basic stepping options.

[weinand]

Does not seem to be an issue any more.

[weinand]

works fine now (even in the presence of watches).