Breakpoints stay on their original line number (do not follow statements) when code is edited during a debug run

[mawright]

This may be an upstream issue with the core VSCode. I don't know Javascript so I'm not able to see if it happens in the built-in debuggers.

Environment data

• VS Code version: 1.26.0
• Extension version (available under the Extensions sidebar): 2018.7.1
• OS and version: Ubuntu 16.04
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.6.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda
• Relevant/affected Python packages and their versions: N/A

Actual behavior

When lines are added/removed in the source code while a debug run is active (i.e., when paused at a breakpoint), all breakpoints stay at their line number and are not moved up or down as lines are added or removed. This means that when the debug run is relaunched, any breakpoints below added/removed lines will be on a different statement than when they were created.
This also means that the behavior of how breakpoints move is different between whether you are editing code while debugging or not. During normal operation, breakpoints move with their statements. During debugging, breakpoints stay in place.

Expected behavior

If code is edited during debugging, breakpoints follow their original statement (moving down 1 line for each line inserted above and up 1 line for each line deleted above) after the debug run is ended.

Steps to reproduce:

1. Non-debug behavior: Breakpoint moves with its original statement c = 3
   

2. Debug behavior: The statement c = 3 begins at line 5, is moved down two lines, but the breakpoint stays at line 5, even after the debug run is completed.
   

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Nothing

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

Nothing

[brettcannon]

This actually isn't under our control and affects TypeScript debugging as well. You can try filing a bug upstream with VS Code itself if you want.