HomeSort by relevance Sort by last modified time
    Searched full:debugger (Results 201 - 225 of 1775) sorted by null

1 2 3 4 5 6 7 891011>>

  /external/v8/test/mjsunit/
debug-mirror-cache.js 53 // Check that mirror cache is cleared when entering debugger.
78 // Enter the debugger twice.
79 debugger;
80 debugger;
  /frameworks/base/docs/html/tools/debugging/
debugging-projects.jd 18 <p>If you are developing in Eclipse with the ADT plugin, you can use the built-in Java Debugger,
19 along with DDMS, to debug your applications. To access the debugger and
20 DDMS, Eclipse displays the debugger and DDMS features as perspectives, which are customized
41 Debug</strong>. Refer to the appropriate documentation for the Eclipse debugger for more
  /frameworks/compile/libbcc/tests/debuginfo/
README 11 by the libbcc driver utility (bcc) on the host through GDB. The debugger
13 Both the debugger commands and the expected output are embedded in the
14 original sources as comments of the form "DEBUGGER: " and "CHECK: ".
63 similar RUN/DEBUGGER/CHECK directives in comments as the existing tests.
  /art/runtime/jdwp/
jdwp_event.h 17 * Handle registration of events, and debugger event notification.
98 uint32_t requestId; /* serial#, reported to debugger */
jdwp_priv.h 22 #include "debugger.h"
75 int clientSock; // Active connection to debugger.
  /dalvik/tests/etc/
reference-run-test-classes 8 # --debug -- wait for debugger to attach
56 msg "Waiting for debugger to connect on localhost:$PORT"
  /external/chromium/chrome/browser/debugger/
devtools_remote_listen_socket.h 11 #include "chrome/browser/debugger/devtools_remote_message.h"
16 // Listens to remote debugger incoming connections, handles the V8ARDP protocol
devtools_remote_message_unittest.cc 9 #include "chrome/browser/debugger/devtools_remote.h"
10 #include "chrome/browser/debugger/devtools_remote_message.h"
  /external/chromium_org/base/debug/
debugger_posix.cc 5 #include "base/debug/debugger.h"
64 LOG(WARNING) << "Starting debugger on pid " << process_id
173 // Our pid is 0 without a debugger, assume this for any pid starting with 0.
187 // We want to break into the debugger in Debug mode, and cause a crash dump in
210 // signals on the general assumption that they are fatal errors. If no debugger
212 // When debugger is attached, for ARM platform the bkpt instruction appears
214 // difficulty continuing in a debugger once we stop from SIG triggered by native
252 // attach the debugger, inspect the state of the program and then resume it by
  /external/chromium_org/components/nacl/common/
nacl_switches.cc 26 // Native Client GDB debugger that will be launched automatically when needed.
29 // GDB script to pass to the nacl-gdb debugger at startup.
  /external/chromium_org/v8/test/mjsunit/regress/
regress-crbug-259300.js 39 exec_state.frame(i).evaluate("debugger", disable_break);
46 eval("debugger");
  /external/chromium_org/v8/test/webkit/
debugger-expected.txt 24 This file tests whether the 'debugger' statement throws a syntax error. (IE respects 'debugger' as a statement that behaves like a breakpoint).
  /external/llvm/bindings/python/
README.txt 31 To step into the Python debugger while running a test, add the following
32 to your test at the point you wish to enter the debugger:
  /external/llvm/lib/ExecutionEngine/RuntimeDyld/
JITRegistrar.h 1 //===-- JITRegistrar.h - Registers objects with a debugger ----------------===//
29 /// debug information for the debugger.
GDBRegistrar.cpp 45 // debugger reads. Make sure to specify the version statically, because the
46 // debugger checks the version before we can set it during runtime.
80 /// debug information for the debugger.
89 /// Deregister the debug info for the given object file from the debugger
132 assert(Buffer && "Attempt to register a null object with a debugger.");
187 // Tell the debugger which entry we removed, and unregister the code.
  /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/schema/
debuggerConnector.exsd 6 <meta.schema plugin="com.android.ide.eclipse.ddms" id="debuggerConnector" name="Debugger Connector"/>
9 Extension Point to provide a way to connect a debugger to a VM running on a connected device.
  /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/src/com/android/ide/eclipse/ddms/
IDebuggerConnector.java 20 * Classes which implement this interface provides a way to connect a debugger to a VM running
33 * Connects a debugger to a VM identified by its appName.
  /dalvik/vm/
Debugger.h 18 * Dalvik-specific side of debugger support. (The JDWP code is intended to
126 * when the debugger attaches.
133 * Returns "true" if a debugger is connected. Returns "false" if it's
139 * Time, in milliseconds, since the last debugger activity. Does not
141 * Returns 0 if we're in the middle of handling a debugger request.
155 * The debugger wants the VM to exit.
261 * Debugger notification
  /external/chromium_org/third_party/skia/gyp/
tools.gyp 386 '../src/utils/debugger',
392 '../src/utils/debugger/SkDrawCommand.h',
393 '../src/utils/debugger/SkDrawCommand.cpp',
394 '../src/utils/debugger/SkDebugCanvas.h',
395 '../src/utils/debugger/SkDebugCanvas.cpp',
396 '../src/utils/debugger/SkObjectParser.h',
397 '../src/utils/debugger/SkObjectParser.cpp',
  /external/skia/gyp/
tools.gyp 386 '../src/utils/debugger',
392 '../src/utils/debugger/SkDrawCommand.h',
393 '../src/utils/debugger/SkDrawCommand.cpp',
394 '../src/utils/debugger/SkDebugCanvas.h',
395 '../src/utils/debugger/SkDebugCanvas.cpp',
396 '../src/utils/debugger/SkObjectParser.h',
397 '../src/utils/debugger/SkObjectParser.cpp',
  /external/chromium_org/v8/test/mjsunit/harmony/
debug-blockscopes.js 203 debugger;
221 debugger;
239 debugger;
257 debugger;
275 debugger;
297 debugger;
319 debugger;
345 debugger;
369 debugger;
392 debugger;
    [all...]
  /external/v8/test/mjsunit/harmony/
debug-blockscopes.js 203 debugger;
221 debugger;
239 debugger;
257 debugger;
275 debugger;
297 debugger;
319 debugger;
345 debugger;
369 debugger;
392 debugger;
    [all...]
  /external/chromium_org/v8/src/
d8-debug.cc 115 // Convert the debugger command to a JSON debugger request.
148 // Convert the debugger response into text details and the running state.
166 RemoteDebugger debugger(isolate, port);
167 debugger.Run();
181 // Connect to the debugger agent.
312 // Convert the debugger command to a JSON debugger request.
329 // Send the JSON debugger request.
  /external/v8/src/
d8-debug.cc 113 // Convert the debugger command to a JSON debugger request.
146 // Convert the debugger response into text details and the running state.
163 RemoteDebugger debugger(port);
164 debugger.Run();
178 // Connect to the debugger agent.
308 // Convert the debugger command to a JSON debugger request.
325 // Send the JSON debugger request.
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/test/impl/
debug.ipp 632 // ************** check if program is running under debugger ************** //
672 // ************** in debugger at call point ************** //
678 // !! ?? auto-start debugger?
704 // If we got here, the user has pushed Debug. Debugger is already attached to our process and we
724 // ************** console debugger setup ************** //
755 // ************** attach debugger to the current process ************** //
769 // Debugger "ready" event
777 // that will signal me that debugger initialization is done
789 // Debugger command line format
805 "Debugger", // name of subkey to quer
    [all...]

Completed in 709 milliseconds

1 2 3 4 5 6 7 891011>>