Breakpoint hit between capturing and replaying erroneously included in a breakpoint scan #240

rjbailey opened this Issue Apr 2, 2013 · 1 comment


None yet
2 participants

rjbailey commented Apr 2, 2013

To reproduce:

  • Create a new recording.
  • After recording stops, hit a breakpoint (while input is still unlocked).
  • Start a breakpoint scan.

The breakpoint will be recorded at the first mark index. Then we get the error described in #239 when the task scheduler attempts to replay to the breakpoint hit we were stopped at.

Screen Shot 2013-04-01 at 5 02 52 PM


burg commented Apr 4, 2013

Hmm, maybe the breakpoint tracker is getting confused.. I'm not happy with the behavior between capture and initial replay, but that's another issue.

burg closed this Apr 1, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment