Lines Matching full:debugger
5380 // Check whether debugger and is about to step into the callback that is passed
8223 // recompilation. This can happen if the debugger is activated and
8227 // If the function is not optimizable or debugger is active continue using the
8235 PrintF(": is code optimizable: %s, is debugger enabled: %s]\n",
10552 isolate->debugger()->SetEventListener(callback, data);
10626 // Get debugger related details for an object property.
10646 // Make sure to set the current context to the context before the debugger was
10647 // entered (if the debugger is entered). The reason for switching context here
10651 // context and not some internal debugger context.
11031 // (e.g. .result)? For users of the debugger, they will probably be
11145 // bit 0: invoked in the debugger context.
11199 // hide this optimization from the debugger, we wrap the receiver
11272 // TODO(yangguo): make sure all code deoptimized when debugger is active
11651 // Catch the case when the debugger stops in an internal function.
12587 // Clear the oneshot breakpoints so that the debugger does not step further.
12685 // Enter the top context from before the debugger was invoked.
12696 // debugger was invoked.
13055 CHECK(isolate->debugger()->live_edit_enabled());
13104 CHECK(isolate->debugger()->live_edit_enabled());
13124 // the script with its original source and sends notification to debugger.
13127 CHECK(isolate->debugger()->live_edit_enabled());
13151 CHECK(isolate->debugger()->live_edit_enabled());
13161 CHECK(isolate->debugger()->live_edit_enabled());
13173 CHECK(isolate->debugger()->live_edit_enabled());
13200 CHECK(isolate->debugger()->live_edit_enabled());
13221 CHECK(isolate->debugger()->live_edit_enabled());
13236 CHECK(isolate->debugger()->live_edit_enabled());
13250 CHECK(isolate->debugger()->live_edit_enabled());
13263 CHECK(isolate->debugger()->live_edit_enabled());
13302 CHECK(isolate->debugger()->live_edit_enabled());
13335 // Calls specified function with or without entering the debugger.
13336 // This is used in unit tests to run code as if debugger is entered or simply
