Don't create debug context if debug listener is not set

test/mjsunit/regress/regress-3960.js

Index: test/mjsunit/regress/regress-3960.js
diff --git a/test/mjsunit/regress/regress-3960.js b/test/mjsunit/regress/regress-3960.js
index 4aaab0b0674b7ae17a6a2a27f979e78673019c25..3387da419d710002d91740ef853e0712b802c1c7 100644
--- a/test/mjsunit/regress/regress-3960.js
+++ b/test/mjsunit/regress/regress-3960.js
@@ -2,13 +2,13 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-// Flags: --allow-natives-syntax
+// Flags: --allow-natives-syntax --expose-debug-as debug

[Yang, 2015/05/11 06:44:19]

This makes this test pointless (see comment). Since %GetDebugContext is only
used in tests, please change it to set a dummy listener to activate the debugger
before getting the debug context (and reset it after).

[yurys, 2015/05/12 06:46:59]

Done. I added DebugScope to Runtime_GetDebugContext.

This sounds weird to me that we allow setting breakpoints when there is no debug
listener. I'd rather we cleared all breakpoints on removing debug listener and
require the client to restore all breakpoints at the beginning of the next debug
session. With current behavior we can set breakpoints during the first debug
session and then hit them in the second session without even knowing that there
are breakpoints. I vaguely recall a bug on this in WebKit but I cannot find it
at the moment.

 
-// Test that setting break point is works correctly when the debugger is
+// Test that setting break point works correctly when the debugger is
 // activated late, which leads to duplicate shared function infos.
 
 (function() {
-  var Debug = %GetDebugContext().Debug;
+  var Debug = debug.Debug;
 
   function listener(event, exec_state, event_data, data) {
     if (event != Debug.DebugEvent.Break) return;