2 Commits

Author	SHA1	Message	Date
turnidge@google.com	383468782e	Keep track of current "pause" event in the debugger. ... This will allow us (later) to make nice descriptions of the state of an isolate, e.g. "isolate 7112 is paused due to breakpoint 2" or "isolate 7112 is paused due to interrupt" or "isolate 7112 is running". Use a new Pause() function to call the event handler during a pause. It does some shared checking, setup, teardown. Minor change in isolate interrupt handling - before we were not setting 'in_event_handler_' in this case. Now we set 'pause_event_' here, which will guard against recursive pauses in this case. Reviewer: not sure what I think about all the names I used here. "pause_event_" is very similar to PausedEvent but means something different, as it includes pauses, interrupts, and (maybe) exceptions. Dunno. R=hausner@google.com Review URL: https://codereview.chromium.org//118603002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@31356 260f80e4-7a28-3924-810f-c04153c831b5	2013-12-20 22:30:23 +00:00
turnidge@google.com	b640712e6b	Handle vmservice messages while at breakpoint. ... Allow rudimentary inspection of breakpoints from vmservice. R=hausner@google.com, johnmccutchan@google.com Review URL: https://codereview.chromium.org//113513004 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@31233 260f80e4-7a28-3924-810f-c04153c831b5	2013-12-18 17:45:17 +00:00