| /external/chromium_org/third_party/skia/src/core/ |
| SkMemory_stdlib.cpp | 45 SkBlockHeader** fTop; // set to verify in debugger that block was alloc'd / freed with same gHeader
46 SkBlockHeader* fPrevious; // set to see in debugger previous block when corruption happens
|
| /external/chromium_org/tools/gyp/pylib/gyp/ |
| MSVSUserFile.py | 21 for an actual file to launch a debugger on, not just a command
111 'DebuggerType': '3', # 'auto' debugger
|
| /external/chromium_org/tools/telemetry/telemetry/core/chrome/ |
| tab_list_backend.py | 16 # Stores web socket debugger URLs in iteration order.
18 # Maps debugger URLs to Tab objects.
|
| /external/chromium_org/v8/test/mjsunit/ |
| debug-listbreakpoints.js | 32 // Note: the following tests only checks the debugger handling of the
33 // setexceptionbreak command. It does not test whether the debugger
|
| /external/eigen/doc/ |
| D11_UnalignedArrayAssert.dox | 28 First of all, you need to find out where in your own code this assertion was triggered from. At first glance, the error message doesn't look helpful, as it refers to a file inside Eigen! However, since your program crashed, if you can reproduce the crash, you can get a backtrace using any debugger. For example, if you're using GCC, you can use the GDB debugger as follows:
|
| /external/llvm/include/llvm/Transforms/ |
| Instrumentation.h | 83 /// displayed in the debugger.
109 /// seen by the debugger.
|
| /external/llvm/lib/Analysis/ |
| CFGPrinter.cpp | 139 /// viewCFG - This function is meant for use from the debugger. You can just
148 /// viewCFGOnly - This function is meant for use from the debugger. It works
|
| /external/skia/src/core/ |
| SkMemory_stdlib.cpp | 45 SkBlockHeader** fTop; // set to verify in debugger that block was alloc'd / freed with same gHeader
46 SkBlockHeader* fPrevious; // set to see in debugger previous block when corruption happens
|
| /external/strace/ |
| PORTING | 24 single-stepping in a debugger with little or nothing to show for it,
39 resolved in a day or two using a decent assembly level debugger and
|
| /external/v8/src/ |
| execution.cc | 795 // If currently in the debugger don't do any actual preemption but record
796 // that preemption occoured while in the debugger.
844 // Don't stop in debugger functions.
876 // Enter the debugger. Just continue if we fail to enter the debugger.
877 EnterDebugger debugger; local
878 if (debugger.FailedToEnter()) {
884 isolate->debugger()->OnDebugBreak(isolate->factory()->undefined_value(),
|
| deoptimizer.h | 116 // debugger to deoptimize stack frames to allow inspection.
117 DEBUGGER
314 // the debugger needs to inspect an optimized frame. For normal
708 // Class used to represent an unoptimized frame when the debugger
711 // by the debugger frame information is copied to an object of this type.
|
| /external/v8/test/mjsunit/ |
| debug-listbreakpoints.js | 32 // Note: the following tests only checks the debugger handling of the
33 // setexceptionbreak command. It does not test whether the debugger
|
| /external/valgrind/main/coregrind/ |
| m_debugger.c | 3 /*--- Attaching a debugger. m_debugger.c ---*/
352 /* Start debugger and get it to attach to this process. Called if the
355 meaningfully get the debugger to continue the program, though; to
356 continue, quit the debugger. */
426 VG_(message)(Vg_UserMsg, "starting debugger with cmd: %s\n", buf);
431 "Debugger has detached. Valgrind regains control."
435 "Warning: Debugger attach failed! (sys_system)\n");
440 "Warning: Debugger attach failed! (ptrace problem?)\n");
|
| /frameworks/base/core/java/android/ddm/ |
| DdmHandleHello.java | 144 * debugger to attach.
186 * is zero, which means "waiting for a debugger".
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/idlelib/ |
| ChangeLog | 52 debugger -i open an interactive shell -i file(s) open a
342 * Debugger.py: py-cvs-rel2_1 (Rev 1.15) merge - whitespace
418 ClassBrowser.py, ColorDelegator.py, Debugger.py, Delegator.py,
435 Debugger.py, Delegator.py, EditorWindow.py, FileList.py,
463 ConfigParser.py, Debugger.py, Delegator.py, EditorWindow.py,
531 ColorDelegator.py, ConfigParser.py, Debugger.py, Delegator.py,
553 ColorDelegator.py, ConfigParser.py, Debugger.py, Delegator.py,
584 Adding the old stack viewer implementation back, for the debugger.
587 (XXX: the debugger doesn't yet use this.)
643 * PyShell.py: Close debugger when closing. This may break a cycle
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/idlelib/ |
| ChangeLog | 52 debugger -i open an interactive shell -i file(s) open a
342 * Debugger.py: py-cvs-rel2_1 (Rev 1.15) merge - whitespace
418 ClassBrowser.py, ColorDelegator.py, Debugger.py, Delegator.py,
435 Debugger.py, Delegator.py, EditorWindow.py, FileList.py,
463 ConfigParser.py, Debugger.py, Delegator.py, EditorWindow.py,
531 ColorDelegator.py, ConfigParser.py, Debugger.py, Delegator.py,
553 ColorDelegator.py, ConfigParser.py, Debugger.py, Delegator.py,
584 Adding the old stack viewer implementation back, for the debugger.
587 (XXX: the debugger doesn't yet use this.)
643 * PyShell.py: Close debugger when closing. This may break a cycle
[all...] |
| /sdk/files/ |
| android.el | 18 "Name of Java debugger."
119 "Start the activity PACKAGE/CLASS within the debugger in the Android emulator. This expects the SDK tools directory to be in the current path."
|
| /frameworks/base/core/java/android/os/ |
| Debug.java | 85 * How long to wait for the debugger to finish sending requests. I've
392 * Wait until a debugger attaches. As soon as the debugger attaches,
406 byte[] data = new byte[] { 0 }; // 0 == "waiting for debugger"
417 System.out.println("Debugger has connected");
420 * There is no "ready to go" signal from the debugger, and we're
421 * not allowed to suspend ourselves -- the debugger expects us to
423 * allow the debugger a chance to set breakpoints before we start
426 * Sit and spin until the debugger has been idle for a short while.
431 System.out.println("debugger detached?")
[all...] |
| /dalvik/vm/interp/ |
| Interp.cpp | 24 * Some debugger support functions are included here.
35 * Debugger support
79 * The debugger may ask us to create the same breakpoint multiple times.
213 * debugger's event request, and we want to be sure that there's exactly
269 * debugger is allowed to insert breakpoints in unverified code,
391 * Do any debugger-attach-time initialization.
408 * Sometimes the debugger likes to add two entries for one breakpoint.
430 * This can be called from the JDWP thread (because the debugger has
574 * we update it on every instruction while the debugger is connected.
708 * Update the debugger on interesting events, such as hitting a breakpoin
[all...] |
| /external/antlr/antlr-3.4/runtime/CSharp2/Sources/Antlr3.Runtime/Antlr.Runtime.Debug/ |
| IDebugEventListener.cs | 111 * triggered by both LA and LT calls. The debugger will want to know
113 * what token was seen at that depth. A remote debugger cannot look
129 * any backtrack), this informs the debugger that stream should be
152 * inform the debugger what line/charPos it is passing in the grammar.
158 * This should also allow breakpoints because the debugger can stop
|
| /external/antlr/antlr-3.4/runtime/CSharp3/Sources/Antlr3.Runtime/Debug/ |
| IDebugEventListener.cs | 113 * triggered by both LA and LT calls. The debugger will want to know
115 * what token was seen at that depth. A remote debugger cannot look
131 * any backtrack), this informs the debugger that stream should be
154 * inform the debugger what line/charPos it is passing in the grammar.
160 * This should also allow breakpoints because the debugger can stop
|
| /external/antlr/antlr-3.4/runtime/Java/src/main/java/org/antlr/runtime/debug/ |
| DebugEventListener.java | 99 * triggered by both LA and LT calls. The debugger will want to know
101 * what token was seen at that depth. A remote debugger cannot look
113 * any backtrack), this informs the debugger that stream should be
132 * inform the debugger what line/charPos it is passing in the grammar.
136 * This should also allow breakpoints because the debugger can stop
|
| /external/chromium_org/third_party/mesa/src/docs/ |
| RELNOTES-5.1 | 104 Vertex/Fragment program debugger
111 The bulk of the vertex/fragment program debugger is implemented
115 The progs/tests/debugger.c (only in CVS) program is an example of how
116 the extension can be used. Presently, the debugger code and demo code
117 is in the same file. Eventually the debugger code should be moved
|
| /external/chromium_org/v8/tools/ |
| js2c.py | 324 debugger = filename.endswith('-debugger.js')
331 if debugger: id = id[:-9]
333 if debugger:
351 # Build debugger support functions
|
| /external/mesa3d/docs/ |
| RELNOTES-5.1 | 104 Vertex/Fragment program debugger
111 The bulk of the vertex/fragment program debugger is implemented
115 The progs/tests/debugger.c (only in CVS) program is an example of how
116 the extension can be used. Presently, the debugger code and demo code
117 is in the same file. Eventually the debugger code should be moved
|
