Add a debugger test for closure breakpoints

Add a debugger test for closure breakpoints

Stop at closure, step into the closure function.

R=asiva@google.com

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

[siva, 2013-05-10 22:02:58]

lgtm

https://codereview.chromium.org/14864024/diff/2001/tests/standalone/debugger/...
File tests/standalone/debugger/closure_debugger_test.dart (right):

https://codereview.chromium.org/14864024/diff/2001/tests/standalone/debugger/...
tests/standalone/debugger/closure_debugger_test.dart:37: SetBreakpoint(15),     
// Breakpoint in bar();
Maybe SetBreakpoint("bar") would be more readable and less prone to errors if
somebody decides to do a mass change of the copyright text.

Similarly 'Step, Step, Step, Step'  instead of SetBreakpoint(22) or have another
top level function whose first statement is the closure call.

[hausner, 2013-05-10 22:46:03]

Committed patchset #2 manually as r22605 (presubmit successful).

[hausner, 2013-05-16 16:32:39]

Apparently forgot to send my responses.

https://codereview.chromium.org/14864024/diff/2001/tests/standalone/debugger/...
File tests/standalone/debugger/closure_debugger_test.dart (right):

https://codereview.chromium.org/14864024/diff/2001/tests/standalone/debugger/...
tests/standalone/debugger/closure_debugger_test.dart:37: SetBreakpoint(15),     
// Breakpoint in bar();
As discussed offline, this is certainly brittle code but unfortunately there is
no solution that is significantly more robust. Ideal would be if a dart program
could get access to its source file and we could put a unique comment in the
line where we want to set a breakpoint.

On 2013/05/10 22:02:58, siva wrote:
> Maybe SetBreakpoint("bar") would be more readable and less prone to errors if
> somebody decides to do a mass change of the copyright text.
> 
> Similarly 'Step, Step, Step, Step'  instead of SetBreakpoint(22) or have
another
> top level function whose first statement is the closure call.