Add debugger safe point on assignment to global variables

Add debugger safe point on assignment to global variables

Just like we do for local variables, add a debug step check (and
thus a breakpoint location) to global variable assignment if
the right side of the assignment has no possible breakpoint locations.

BUG=#27287
R=johnmccutchan@google.com

Committed: https://github.com/dart-lang/sdk/commit/0dd760092d808bd387852204f30e4a2ba398b01f

[hausner, 2016-09-19 23:27:17]

Description was changed from

==========
Add debugger safe point on assignment to global variables

Just like we do for local variables, add a debug step check (and
thus a breakpoint location) to global variable assignment if
the right side of the assignment has no possible breakpoint locations.

BUG=#27287
==========

to

==========
Add debugger safe point on assignment to global variables

Just like we do for local variables, add a debug step check (and
thus a breakpoint location) to global variable assignment if
the right side of the assignment has no possible breakpoint locations.

BUG=#27287
==========

[hausner, 2016-09-19 23:27:17]

hausner@google.com changed reviewers:
+ johnmccutchan@google.com

[Cutch, 2016-09-20 18:36:24]

LGTM after adding a regression service protocol test.

[hausner, 2016-09-20 21:05:48]

Description was changed from

==========
Add debugger safe point on assignment to global variables

Just like we do for local variables, add a debug step check (and
thus a breakpoint location) to global variable assignment if
the right side of the assignment has no possible breakpoint locations.

BUG=#27287
==========

to

==========
Add debugger safe point on assignment to global variables

Just like we do for local variables, add a debug step check (and
thus a breakpoint location) to global variable assignment if
the right side of the assignment has no possible breakpoint locations.

BUG=#27287
R=johnmccutchan@google.com

Committed:
https://github.com/dart-lang/sdk/commit/0dd760092d808bd387852204f30e4a2ba398b01f
==========

[hausner, 2016-09-20 21:05:50]

Committed patchset #2 (id:20001) manually as
0dd760092d808bd387852204f30e4a2ba398b01f (presubmit successful).