Stepping/Continuing after modifying a source file does not give the debugger any updated information

[wesrupert]

• VSCode Version: 1.4.0-Insider 2016-07-26T05:09:25.359Z

Steps to Reproduce:

1. Set and hit a breakpoint in a C# app
2. Write gibberish after the breakpoint, as many lines of it as you like
3. Step over

Expected Result:

• Stepping leads to a no source page

Actual Result:

• Stepping steps into garbage lines, as the debugger has no idea that the expected lines aren't there

I'm not seeing an event come in indicating that we are now working with stale code in the window. It looks like Issue 8077 improved this behavior when the user saves, but now we need something to enable correct behavior, e.g. a "no source" page since the window no longer represents the code that the debugger thinks it's running.

[remss]

I don't see how we can detect that breakpoints must not be applied/verified on setBreakpoints request when the source is dirty and not saved yet.
Can the sourceModified flag be set to TRUE is this case ?

[weinand]

As soon as source is edited while a debug session is active, the breakpoints are marked as unverified and rendered as such.

[remss]

Yes when file is dirty breakpoints are marked as unverified in the GUI but the debugger will still break on old source breakpoints (on empty lines).
I this case I believe that the paused source cannot be the local one any more but should be a read-only loaded script tab, with current active breakpoints displayed.