Run to cursor to a previously executed line results in a leaked breakpoint

[edumunoz]

• VSCode Version: 1.2.0
• OS Version: OS X

I understand this is a result of the implementation of RunToCursorAction, which basically creates a breakpoint at the specified location, continues the execution, and remove the breakpoint once it has been hit.

Steps to Reproduce:

1. Set a breakpoint and start debugging.
2. Select Run to cursor in the context menu for a line that won't be executed
3. Stop the program

Result: there is a leaked breakpoint where run to cursor was called.

@isidorn @weinand

[edumunoz]

I opened PR #7367.

The best experience would also hide these breakpoints from the UI.

[weinand]

@isidorn we should clear all temporary breakpoints after the program has stopped again (step 3 from above)

[weinand]

while verifying this I found #8731