Add a separate test verifying that the optimizer does not trip over debug break.

Add a separate test verifying that the optimizer does not trip over debug break.

R=iposva@google.com

Committed: https://code.google.com/p/dart/source/detail?r=45300

[regis, 2015-04-16 22:59:41]

regis@google.com changed reviewers:
+ iposva@google.com

[regis, 2015-04-16 23:00:57]

Still not optimal, but testing a bit more.

[Ivan Posva, 2015-04-20 22:05:14]

LGTM -ip

https://codereview.chromium.org/1091133002/diff/40001/tests/language/vm/debug...
File tests/language/vm/debug_break_enabled_vm_test.dart (right):

https://codereview.chromium.org/1091133002/diff/40001/tests/language/vm/debug...
tests/language/vm/debug_break_enabled_vm_test.dart:13: if (i == 18) break "hit";
  / / / 01: crash
As discussed we can execute this piece of code on the VM by setting a Crash, OK
expectation in the status files.

[regis, 2015-04-20 23:17:59]

Thanks!

https://codereview.chromium.org/1091133002/diff/40001/tests/language/vm/debug...
File tests/language/vm/debug_break_enabled_vm_test.dart (right):

https://codereview.chromium.org/1091133002/diff/40001/tests/language/vm/debug...
tests/language/vm/debug_break_enabled_vm_test.dart:13: if (i == 18) break "hit";
  / / / 01: crash
On 2015/04/20 22:05:14, Ivan Posva wrote:
> As discussed we can execute this piece of code on the VM by setting a Crash,
OK
> expectation in the status files.

Good idea. Done.

[regis, 2015-04-20 23:20:09]

Committed patchset #4 (id:60001) manually as r45300 (presubmit successful).