| /external/kernel-headers/original/asm-x86/ |
| vm86.h | 53 #define VM86_TRAP 6 /* return due to DOS-debugger request */
122 unsigned long vm86dbg_active:1; /* for debugger */
123 unsigned long vm86dbg_TFpendig:1; /* for debugger */
126 unsigned char vm86dbg_intxxtab[32]; /* for debugger */
|
| /external/mesa3d/src/gallium/auxiliary/rbug/ |
| rbug.h | 26 * Include all for users the remote debugger protocol code.
|
| /external/mesa3d/src/gallium/drivers/rbug/ |
| README | 6 This directory contains a Gallium3D remote debugger pipe driver.
|
| /external/mesa3d/src/gallium/drivers/trace/ |
| README | 6 This directory contains a Gallium3D trace debugger pipe driver.
|
| /external/smack/asmack-master/static-src/custom/de/measite/smack/ |
| AndroidDebugger.java | 3 import org.jivesoftware.smack.debugger.SmackDebugger;
18 * Very simple debugger that prints to the android log the sent and received stanzas. Use
19 * this debugger with caution since printing to the console is an expensive operation that may
164 // Add the connection listener to the connection so that the debugger can be notified
|
| /external/smack/src/de/measite/smack/ |
| AndroidDebugger.java | 3 import org.jivesoftware.smack.debugger.SmackDebugger;
18 * Very simple debugger that prints to the android log the sent and received stanzas. Use
19 * this debugger with caution since printing to the console is an expensive operation that may
164 // Add the connection listener to the connection so that the debugger can be notified
|
| /external/smack/src/org/jivesoftware/smack/debugger/ |
| ConsoleDebugger.java | 18 package org.jivesoftware.smack.debugger;
32 * Very simple debugger that prints to the console (stdout) the sent and received stanzas. Use
33 * this debugger with caution since printing to the console is an expensive operation that may
178 // Add the connection listener to the connection so that the debugger can be notified
|
| /external/v8/test/mjsunit/ |
| debug-evaluate-recursive.js | 134 // Test functions - one with break point and one with debugger statement.
140 debugger;
147 debugger;
162 debugger;
|
| /external/valgrind/main/ |
| valgrind.spec.in | 1 Summary: Valgrind Memory Debugger
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/launch/ |
| EmptyLaunchAction.java | 41 // return false so launch controller will not wait for debugger to attach
|
| IAndroidLaunchAction.java | 33 * @returns true if launch was successfully, and controller should wait for debugger to attach
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/ |
| plugin.properties | 18 extension-point.name.Debugger_Connector = Debugger Connector
|
| /system/core/include/cutils/ |
| misc.h | 31 /* Connects your process to the system debugger daemon
|
| /art/runtime/jdwp/ |
| jdwp_adb.cc | 44 * a given JDWP debugger, that can be used to read the usual
131 * directly with a debugger or DDMS.
177 * Block forever, waiting for a debugger to connect to us. Called from the
289 * connections if we already have a debugger attached. If we don't, the
290 * debugger will just mysteriously hang until it times out. We could just
371 LOG(INFO) << "Ignoring second debugger -- accepting and dropping";
410 * the debugger, no matter who connects to whom.
|
| /external/chromium_org/chrome/nacl/ |
| nacl_helper_linux.cc | 146 // usual way, the debugger cannot figure out where our executable
152 // structure. The debugger will look for that symbol by name to
158 // debugger never change. So we just copy the contents of the
160 // Hereafter, if someone attaches a debugger (or examines a core dump),
161 // the debugger will find all the symbols in the normal way.
173 // have a dynamic section, the debugger will not skip the
177 // normal for the main executable. So the debugger doesn't
|
| /external/chromium_org/third_party/skia/gyp/ |
| SampleApp.gyp | 17 '../src/utils/debugger',
23 '../src/utils/debugger/SkDrawCommand.h',
24 '../src/utils/debugger/SkDrawCommand.cpp',
25 '../src/utils/debugger/SkDebugCanvas.h',
26 '../src/utils/debugger/SkDebugCanvas.cpp',
27 '../src/utils/debugger/SkObjectParser.h',
28 '../src/utils/debugger/SkObjectParser.cpp',
|
| /external/skia/gyp/ |
| SampleApp.gyp | 17 '../src/utils/debugger',
23 '../src/utils/debugger/SkDrawCommand.h',
24 '../src/utils/debugger/SkDrawCommand.cpp',
25 '../src/utils/debugger/SkDebugCanvas.h',
26 '../src/utils/debugger/SkDebugCanvas.cpp',
27 '../src/utils/debugger/SkObjectParser.h',
28 '../src/utils/debugger/SkObjectParser.cpp',
|
| /external/chromium_org/third_party/WebKit/Source/core/inspector/ |
| InspectorDOMDebuggerAgent.cpp | 98 // Browser debugger agent enabled only when JS debugger is enabled.
199 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::DOM, eventData.release());
299 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::DOM, eventData.release());
309 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::DOM, eventData.release());
313 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::DOM, eventData.release());
323 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::DOM, eventData.release());
389 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::EventListener, eventData);
391 m_debuggerAgent->schedulePauseOnNextStatement(InspectorFrontend::Debugger::Reason::EventListener, eventData);
513 m_debuggerAgent->breakProgram(InspectorFrontend::Debugger::Reason::XHR, eventData.release())
[all...] |
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/idlelib/ |
| HISTORY.txt | 25 particularly with running things from the shell window. Also the debugger is
146 - debugger (not complete, but you can set breakpoints, view and step)
178 Viewer menu, not by the debugger.)
222 - Enabled support for running a module, with or without the debugger.
224 reload of that module; Control-F5 loads it under the debugger.
230 with "!"); use this for the Debugger and "Auto-open stack viewer"
233 - Added a Quit button to the Debugger API.
237 - Fix the debugger (when using Python 1.5.2b2) to use canonical
240 debugger though.)
247 - Bind ESC to "close window" of the debugger, stack viewer and clas
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/idlelib/ |
| HISTORY.txt | 25 particularly with running things from the shell window. Also the debugger is
146 - debugger (not complete, but you can set breakpoints, view and step)
178 Viewer menu, not by the debugger.)
222 - Enabled support for running a module, with or without the debugger.
224 reload of that module; Control-F5 loads it under the debugger.
230 with "!"); use this for the Debugger and "Auto-open stack viewer"
233 - Added a Quit button to the Debugger API.
237 - Fix the debugger (when using Python 1.5.2b2) to use canonical
240 debugger though.)
247 - Bind ESC to "close window" of the debugger, stack viewer and clas
[all...] |
| /external/chromium/chrome/browser/extensions/ |
| extension_debugger_api.cc | 5 // Implements the Chrome Extensions Debugger API.
17 #include "chrome/browser/debugger/devtools_client_host.h"
18 #include "chrome/browser/debugger/devtools_manager.h"
118 // Detach from debugger when extension unloads.
122 // Attach to debugger and tell it we are ready.
|
| /frameworks/compile/libbcc/lib/ExecutionEngine/ |
| GDBJITRegistrar.cpp | 47 // It is expected that a debugger (plugin) sets this
61 // debugger reads. Make sure to specify the version statically, because the
62 // debugger checks the version before we can set it during runtime.
103 /// Deregister the debug info for the given object file from the debugger
157 assert(Object && "Attempt to register a null object with a debugger.");
|
| /dalvik/docs/ |
| debugmon.html | 97 between a VM and a debugger). To a
98 non-DDM client, the DDM server just looks like a debugger.
105 events do not elicit a response from the debugger, meaning the client
109 from the debugger side include a serial number, which the VM includes
112 debugger traffic.
117 <li>The VM only expects one connection from a debugger, so you couldn't
118 attach the monitor and a debugger at the same time. This will be
119 worked around by connecting the debugger to the monitor and passing the
124 <li>The VM behaves differently when a debugger is attached. It will
125 run more slowly, and any objects passed to the monitor or debugger ar
[all...] |
| /dalvik/vm/jdwp/ |
| JdwpAdb.cpp | 38 * a given JDWP debugger, that can be used to read the usual
129 * directly with a debugger or DDMS.
180 * Block forever, waiting for a debugger to connect to us. Called from the
291 * Connect out to a debugger (for server=n). Not required.
299 * Close a connection from a debugger (which may have already dropped us).
369 * Is a debugger connected to us?
466 ALOGE("Failed sending reply to debugger: %s", strerror(errno));
492 * connections if we already have a debugger attached. If we don't, the
493 * debugger will just mysteriously hang until it times out. We could just
576 ALOGI("Ignoring second debugger -- accepting and dropping")
[all...] |
| /external/antlr/antlr-3.4/runtime/C/src/ |
| antlr3commontreeadaptor.c | 57 static void setDebugEventListener (pANTLR3_BASE_TREE_ADAPTOR adaptor, pANTLR3_DEBUG_EVENT_LISTENER debugger);
177 ANTLR3_TREE_ADAPTORDebugNew(pANTLR3_STRING_FACTORY strFactory, pANTLR3_DEBUG_EVENT_LISTENER debugger)
189 antlr3BaseTreeAdaptorInit(ta, debugger);
202 setDebugEventListener (pANTLR3_BASE_TREE_ADAPTOR adaptor, pANTLR3_DEBUG_EVENT_LISTENER debugger)
206 antlr3BaseTreeAdaptorInit(adaptor, debugger);
277 adaptor->debugger->createNode(adaptor->debugger, ct);
415 adaptor->debugger->setTokenBoundaries(adaptor->debugger, t, startToken->getTokenIndex(startToken), stopToken->getTokenIndex(stopToken));
|
