HomeSort by relevance Sort by last modified time
    Searched full:debugging (Results 751 - 775 of 5654) sorted by null

<<31323334353637383940>>

  /external/chromium_org/third_party/npapi/npspy/extern/nspr/md/
_win95.h 110 PRUint32 magic; /* for debugging */
121 PRUint32 magic; /* for debugging */
125 PRUint32 magic; /* for debugging */
135 PRUint32 magic; /* for debugging */
144 PRUint32 magic; /* for debugging */
  /frameworks/base/core/java/android/util/
TimeUtils.java 365 /** @hide Just for debugging; not internationalized. */
373 /** @hide Just for debugging; not internationalized. */
381 /** @hide Just for debugging; not internationalized. */
386 /** @hide Just for debugging; not internationalized. */
395 /** @hide Just for debugging; not internationalized. */
  /frameworks/base/docs/html/tools/help/
monkey.jd 27 <li>Debugging options.</li>
176 <td rowspan="8">Debugging</td>
190 <a href="{@docRoot}tools/debugging/debugging-tracing.html" title="traceview">Traceview</a> for more information
237 <!-- TODO: add a section called "debugging" that covers ways to use it,
adt.jd 59 debugging</strong></dt>
102 <li><a href="{@docRoot}tools/debugging/debugging-tracing.html">Traceview</a>:
110 <li><a href="{@docRoot}tools/debugging/debugging-ui.html#HierarchyViewer">Hierarchy
114 <li><a href="{@docRoot}tools/debugging/debugging-ui.html#pixelperfect">Pixel
118 <li><a href="{@docRoot}tools/debugging/ddms.html">DDMS</a>: Provides
119 debugging features including: screen capturing, thread and heap information, and logcat
  /ndk/docs/text/
OVERVIEW.text 261 project path (Note that unstripped versions are kept for debugging
327 ### V. Debugging support:
330 a native debugging session of your applications.
332 Native debugging can *ONLY* be performed on production devices running
336 For more information, read docs/NDK-GDB.html. In a nutshell, native debugging
  /external/chromium/chrome/common/extensions/docs/
tut_debugging.html 19 <title>Tutorial: Debugging - Google Chrome Extensions - Google Code</title></head>
219 <li class="leftNavSelected">Debugging</li>
254 <h1 class="page_title">Tutorial: Debugging</h1>
343 <div id="static"><div id="pageData-name" class="pageData">Tutorial: Debugging</div>
554 Now that you've been introduced to debugging,
561 <a href="http://www.youtube.com/watch?v=IP0nMv_NI1s&amp;feature=PlayList&amp;p=CA101D6A85FE9D4B&amp;index=5">Developing and Debugging</a>.
569 Try using widely available debugging APIs such as
  /external/clang/www/
hacking.html 27 <li><a href="#debugging">Debugging</a></li>
52 or other information using <tt>cstdio</tt>; debugging routines should
76 <h2 id="debugging">Debugging</h2>
97 <h3 id="debuggingVisualStudio">Debugging using Visual Studio</h3>
100 <p>The file <tt>utils/clangVisualizers.txt</tt> provides debugger visualizers that make debugging
  /external/guava/guava-tests/test/com/google/common/base/
SplitterTest.java 89 "Testing-rocks-Debugging-sucks");
91 "Testing", "rocks", "Debugging", "sucks");
99 "Testing", "rocks", "Debugging", "sucks");
190 "Testing-rocks-Debugging-sucks");
192 "Testing", "rocks", "Debugging", "sucks");
325 "Testing-rocks-Debugging-sucks");
326 ASSERT.that(testPatterningMotto).hasContentsInOrder("Testing", "rocks", "Debugging", "sucks");
  /external/valgrind/main/docs/xml/
manual-core-adv.xml 17 <listitem><para>Debugging your program using Valgrind's gdbserver
95 range. Useful if you are debugging a JIT compiler or some other
281 xreflabel="Debugging your program using Valgrind's gdbserver and GDB">
282 <title>Debugging your program using Valgrind gdbserver and GDB</title>
298 <title>Quick Start: debugging in 3 steps</title>
349 of this "GDB remote debugging" protocol. To debug a process running
420 Remote debugging using | vgdb
441 Remote debugging using | vgdb
448 Remote debugging using | vgdb --pid=2479
459 in the same way as if you were debugging the program natively:</para
    [all...]
  /frameworks/rs/cpp/util/
RefBase.h 73 //! DEBUGGING ONLY: Get current strong ref count.
92 //! DEBUGGING ONLY: Get current weak ref count.
95 //! DEBUGGING ONLY: Print references held on object.
98 //! DEBUGGING ONLY: Enable tracking for this object.
112 //! DEBUGGING ONLY: Print references held on object.
115 //! DEBUGGING ONLY: Enable tracking of object.
176 //! DEBUGGING ONLY: Get current strong ref count.
  /frameworks/rs/server/
RefBase.h 72 //! DEBUGGING ONLY: Get current strong ref count.
91 //! DEBUGGING ONLY: Get current weak ref count.
94 //! DEBUGGING ONLY: Print references held on object.
97 //! DEBUGGING ONLY: Enable tracking for this object.
111 //! DEBUGGING ONLY: Print references held on object.
114 //! DEBUGGING ONLY: Enable tracking of object.
175 //! DEBUGGING ONLY: Get current strong ref count.
  /system/core/include/utils/
RefBase.h 77 //! DEBUGGING ONLY: Get current strong ref count.
96 //! DEBUGGING ONLY: Get current weak ref count.
99 //! DEBUGGING ONLY: Print references held on object.
102 //! DEBUGGING ONLY: Enable tracking for this object.
116 //! DEBUGGING ONLY: Print references held on object.
119 //! DEBUGGING ONLY: Enable tracking of object.
186 //! DEBUGGING ONLY: Get current strong ref count.
  /external/antlr/antlr-3.4/runtime/Python/antlr3/
debug.py 202 """A TreeAdaptor proxy that fires debugging events to a DebugEventListener
205 in generated rules. Debugging events are triggered *after* invoking
400 """All debugging events that a recognizer can trigger.
402 I did not create a separate AST debugging interface as it would create
406 possible events. Hopefully, adding ST debugging stuff won't be bad. Leave
541 Across a socket for remote debugging, only the RecognitionException
625 remote debugging listeners that it's time to quit. When the rule
741 Useful for debugging the debugging facility ;)
    [all...]
  /external/chromium_org/native_client_sdk/src/doc/sdk/
release-notes.rst 367 <https://developers.google.com/native-client/pepper23/devguide/devcycle/debugging#gdb>`_
458 Native Client modules. See :ref:`Debugging with nacl-gdb
459 <devcycle-debugging>` for instructions on how to use this debugger. For now,
510 <http://www.chromium.org/nativeclient/how-tos/debugging-documentation/debugging-a-trusted-plugin/trusted-debugging-on-mac>`_
512 <http://www.chromium.org/nativeclient/how-tos/debugging-documentation/debugging-a-trusted-plugin/debugging-a-trusted-plugin-on-linux>`_.
  /dalvik/dexgen/src/com/android/dexgen/dex/file/
AnnotationsDirectoryItem.java 199 * meant for use by debugging / dumping code.
220 * meant for use by debugging / dumping code.
354 * Prints out the contents of this instance, in a debugging-friendly
ClassDefItem.java 367 * meant for use by debugging / dumping code.
378 * meant for use by debugging / dumping code.
388 * Prints out the contents of this instance, in a debugging-friendly
  /dalvik/dx/src/com/android/dx/dex/file/
AnnotationsDirectoryItem.java 198 * meant for use by debugging / dumping code.
219 * meant for use by debugging / dumping code.
353 * Prints out the contents of this instance, in a debugging-friendly
ClassDefItem.java 364 * meant for use by debugging / dumping code.
375 * meant for use by debugging / dumping code.
385 * Prints out the contents of this instance, in a debugging-friendly
  /docs/source.android.com/src/source/
building-running.jd 55 <p>The example above refers to a complete build for the emulator, with all debugging enabled.</p>
100 <td>like "user" but with root access and debuggability; preferred for debugging</td>
104 <td>development configuration with additional debugging tools</td>
using-eclipse.jd 137 <h2 id="debugging-the-emulator-with-eclipse">Debugging the emulator with Eclipse</h2>
150 <p>You should see a splufty debugging console.</p>
  /external/chromium_org/third_party/icu/source/test/perf/DateFmtPerf/
DateFmtPerf.h 124 // Print the given string to stdout (for debugging purposes)
210 // Print the given string to stdout (for debugging purposes)
339 // Print the given string to stdout using the UTF-8 converter (for debugging purposes only)
  /external/chromium_org/third_party/tcmalloc/chromium/src/tests/
debugallocation_test.cc 185 // This test can only be run if debugging.
187 // If not debugging, the 'new' following the dangling write might not be
188 // safe. When debugging, we expect the (trashed) deleted block to be on the
  /external/chromium_org/third_party/tcmalloc/vendor/src/tests/
debugallocation_test.cc 185 // This test can only be run if debugging.
187 // If not debugging, the 'new' following the dangling write might not be
188 // safe. When debugging, we expect the (trashed) deleted block to be on the
  /external/clang/lib/StaticAnalyzer/
README.txt 104 = Debugging the Analyzer =
106 There are some useful command-line options for debugging. For example:
117 extremely useful when debugging the analyzer and viewing the
  /external/dexmaker/src/dx/java/com/android/dx/dex/file/
AnnotationsDirectoryItem.java 199 * meant for use by debugging / dumping code.
220 * meant for use by debugging / dumping code.
354 * Prints out the contents of this instance, in a debugging-friendly

Completed in 2073 milliseconds

<<31323334353637383940>>