[Win10] After __debugbreak(), the debugger no longer works correctly

Environment:

• tool-chain: C++ tool-chain that comes with Visual Studio 2015.
• VSCode 1.12.2
• Windows 10.

Steps to reproduce:

1. Add __debugBreak somewhere in your C++ code.
2. Start a debugging session until the execution stops in the __debugBreak() call.
3. From this moment on, try to go step-by-step in the code (using F10)

Expected result:
The debugger should step by step into the code, and the execution cursor (yellow arrow at the left side of the editor pane while in the Debugger view) should show the currently executed line.

Actual result:
The debugger goes step by step into the code, but the execution cursor disappears after the first F10 key-press. After this point you don't know where the execution cursor is.

Recovery:
The only way to recover from this is to look into the call-stack view, select the current thread, and double click the function at the top of the call-stack. After this action, the execution cursor reappears, but only until you press F10 again, when it disappears.

Mention:
This only happens after __debugBreak(). For a normal breakpoint added with F9 the debugger works correctly.

Riprodurre il problema con l’ambiente indicato, composto da Visual Studio 2015, VS Code 1.12.2 e Windows 10, usando un programma C++ contenente __debugBreak(), quindi confrontare l’esecuzione passo-passo con un normale punto di interruzione F9. Tracciare gli aggiornamenti del thread corrente e della posizione di esecuzione del debugger dopo F10; il lavoro è completato quando il cursore di esecuzione rimane visibile e accurato dopo ogni passo.