When the program is running and you set a breakpoint, VICE remotemon pauses the app (at whereever it happened to be running when break was set). Once you continue with 'c' or 'g' from this point, the actual breakpoint will be hit.
It'd be better if setting a breakpoint wouldn't immediately pause but rather it'd continue and then let VICE break on actual breakpoints.
Maybe should change MonitorConnection API from setBreakpoint to setBreakpoints which'd also delete earlier breakpoints and reset the whole array and then resume execution.
When the program is running and you set a breakpoint, VICE remotemon pauses the app (at whereever it happened to be running when break was set). Once you continue with 'c' or 'g' from this point, the actual breakpoint will be hit.
It'd be better if setting a breakpoint wouldn't immediately pause but rather it'd continue and then let VICE break on actual breakpoints.
Maybe should change MonitorConnection API from setBreakpoint to setBreakpoints which'd also delete earlier breakpoints and reset the whole array and then resume execution.