Debugging breakpoints broken after hot reload on the web

[biggs0125]

Handle re-registering breakpoints after a hot reload based on new code locations.

[srujzs]

dart-lang/webdev#2606 disables them on changed files for now. We're working on getting them working and reregistered still.

[bkonyi]

Handle re-registering breakpoints after a hot reload based on new code locations.

FWIW, the VM doesn't try and re-register breakpoints in changed libraries. It's up to the service clients to reset them after the reload completes.

[srujzs]

FWIW, the VM doesn't try and re-register breakpoints in changed libraries. It's up to the service clients to reset them after the reload completes.

Agreed. We chatted about this, but DWDS still needs to send the right events for the client to do so. I've tried that (in combination with the expected pause), but the program doesn't resume so I need to debug further on where things are going wrong. And separately, the breakpoint mapping on files seems off so I'll need to fix that.