| /ndk/tests/build/issue20862-libpng-O0/jni/ |
| pngdebug.h | 2 /* pngdebug.h - Debugging macros for libpng, also used in pngtest.c
15 /* Define PNG_DEBUG at compile time for debugging information. Higher
16 * numbers for PNG_DEBUG mean more debugging information. This has
|
| /packages/providers/CalendarProvider/src/com/android/providers/calendar/ |
| CalendarDebug.java | 36 * Displays info about all the user's calendars, for debugging.
74 * Fetches debugging info from the database
151 * Runs on the UI thread to display the debugging info.
|
| /prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/lib/gcc/x86_64-w64-mingw32/4.8.3/plugin/include/ |
| flag-types.h | 37 DINFO_LEVEL_NONE, /* Write no debugging info. */
63 idea is to not emit struct debugging information in the current
74 struct debugging information.
|
| /prebuilts/python/darwin-x86/2.7.5/include/python2.7/ |
| pymem.h | 29 memory functions in special debugging wrappers that add additional
30 debugging info to dynamic memory blocks. The system routines have no idea
61 /* Redirect all memory operations to Python's debugging allocator. */
|
| /prebuilts/python/linux-x86/2.7.5/include/python2.7/ |
| pymem.h | 29 memory functions in special debugging wrappers that add additional
30 debugging info to dynamic memory blocks. The system routines have no idea
61 /* Redirect all memory operations to Python's debugging allocator. */
|
| /external/chromium_org/components/query_parser/ |
| snippet.cc | 180 // Switch to DCHECK after debugging http://crbug.com/15261.
240 // Switch to DCHECK after debugging http://crbug.com/15261.
251 // Switch to DCHECK after debugging http://crbug.com/15261.
271 // Switch to DCHECK after debugging http://crbug.com/15261.
279 // Switch to DCHECK after debugging http://crbug.com/15261.
|
| /external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/ |
| vs-addin.rst | 4 Debugging With Visual Studio
68 ?start debugging? command, Visual Studio automatically launches a web server to
171 module, and to the Chrome browser that you choose to use for debugging.
273 Use the debugging command (F5) to build and run the project. As the wheels
282 * "Debugging information for chrome.exe cannot be found." This is to be
283 expected, you are debugging your module's code, not Chrome.
293 #. The Visual Studio output window displays debugging messages when you select
295 Stop the debugging session by closing the Chrome window, or select the stop
296 debugging command from the debug menu. The nacl-gdb window will close when
310 details, see :ref:`Debugging with nacl-gdb <using_gdb>` (scroll down to the en
[all...] |
| /external/valgrind/main/docs/xml/ |
| valgrind-manpage.xml | 17 <refpurpose>a suite of tools for debugging and profiling programs</refpurpose>
33 <para><command>Valgrind</command> is a flexible program for debugging
35 a synthetic CPU in software, and a series of debugging and profiling tools.
118 <refsect1 id="debugging-valgrind-options">
119 <title>Debugging Valgrind Options</title>
|
| /packages/apps/Email/src/com/android/email/provider/ |
| DBHelper.java | [all...] |
| /docs/source.android.com/src/devices/tech/dalvik/ |
| art.jd | 83 href="http://developer.android.com/tools/debugging/debugging-memory.html#LogMessages"><code>GC_FOR_ALLOC</code></a>
95 <h3 id="Debugging_Imp">Development and debugging improvements</h3>
97 <p>ART offers a number of features to improve app development and debugging.</p>
113 <h4 id="Debugging_Features">Support for more debugging features</h4>
115 <p>ART supports a number of new debugging options, particularly in monitor- and
200 <li><em>Debug-time issue:</em> Interactive debugging performance was slow,
|
| /external/e2fsprogs/ |
| configure.in | 410 [ --enable-jbd-debug enable journal debugging],
413 AC_MSG_RESULT([Disabling journal debugging])
416 [Define to 1 if debugging ext3/4 journal code])
417 AC_MSG_RESULT([Enabling journal debugging])
420 AC_MSG_RESULT([Disabling journal debugging by default])
426 [ --enable-blkid-debug enable blkid debugging],
429 AC_MSG_RESULT([Disabling blkid debugging])
432 [Define to 1 if debugging the blkid library])
433 AC_MSG_RESULT([Enabling blkid debugging])
436 AC_MSG_RESULT([Disabling blkid debugging by default]
[all...] |
| /frameworks/base/services/core/java/com/android/server/am/ |
| ProcessRecord.java | 128 String adjType; // Debugging: primary thing impacting oom_adj.
129 int adjTypeCode; // Debugging: adj code to report to app.
130 Object adjSource; // Debugging: option dependent object.
131 int adjSourceProcState; // Debugging: proc state of adjSource's process.
132 Object adjTarget; // Debugging: target component impacting oom_adj.
162 boolean debugging; // was app launched for debugging? field in class:ProcessRecord
312 if (debugging || crashing || crashDialog != null || notResponding
314 pw.print(prefix); pw.print("debugging="); pw.print(debugging);
[all...] |
| /dalvik/dexgen/src/com/android/dexgen/rop/code/ |
| Rop.java | 76 /** {@code null-ok;} nickname, if specified (used for debugging) */
92 * @param nickname {@code null-ok;} optional nickname (used for debugging)
139 * @param nickname {@code null-ok;} optional nickname (used for debugging)
157 * @param nickname {@code null-ok;} optional nickname (used for debugging)
174 * @param nickname {@code null-ok;} optional nickname (used for debugging)
192 * @param nickname {@code null-ok;} optional nickname (used for debugging)
|
| /dalvik/dx/src/com/android/dx/rop/code/ |
| Rop.java | 76 /** {@code null-ok;} nickname, if specified (used for debugging) */
92 * @param nickname {@code null-ok;} optional nickname (used for debugging)
139 * @param nickname {@code null-ok;} optional nickname (used for debugging)
157 * @param nickname {@code null-ok;} optional nickname (used for debugging)
174 * @param nickname {@code null-ok;} optional nickname (used for debugging)
192 * @param nickname {@code null-ok;} optional nickname (used for debugging)
|
| /external/chromium_org/native_client_sdk/src/doc/sdk/ |
| examples.rst | 149 .nexe files, for ease of debugging. All Debug and Release directories contain
236 Debugging the SDK examples
256 Remote debugging using :4014
261 ``next``, ``break`` and ``backtrace``. See :doc:`Debugging
262 <../devguide/devcycle/debugging>` for more information about debugging a Native Client
|
| /external/chromium_org/third_party/yasm/source/patched-yasm/frontends/yasm/ |
| yasm.xml | 69 source debugging information in STABS, DWARF 2, and CodeView 8
150 Select debugging format</term>
153 <para>Selects the debugging format for debug information.
154 Debugging information can be used by a debugger to associate
160 available debugging formats to standard output, use
168 for a list of supported debugging formats.</para>
|
| /external/chromium_org/third_party/yasm/source/patched-yasm/modules/dbgfmts/stabs/ |
| stabs-dbgfmt.c | 2 * Stabs debugging format
340 N_("stabs debugging conflicts with user-defined section .stab"));
345 N_("stabs debugging overrides empty section .stab"));
356 N_("stabs debugging conflicts with user-defined section .stabstr"));
361 N_("stabs debugging overrides empty section .stabstr"));
505 "Stabs debugging format",
|
| /external/chromium_org/third_party/yasm/source/patched-yasm/ |
| yasm.1 | 32 (2 or 3 clause) BSD license\&. Yasm currently supports the x86 and AMD64 instruction sets, accepts NASM and GAS assembler syntaxes, outputs binary, ELF32, ELF64, COFF, Win32, and Win64 object formats, and generates source debugging information in STABS, DWARF 2, and CodeView 8 formats\&.
92 \fB\-g \fR\fB\fIdebug\fR\fR or \fB\-\-dformat=\fR\fB\fIdebug\fR\fR: Select debugging format
94 Selects the debugging format for debug information\&. Debugging information can be used by a debugger to associate executable code back to the source file or get data structure and type information\&. Available debug formats vary between different object formats;
96 will error when an invalid combination is selected\&. The default object format is selected by the object format\&. To print a list of available debugging formats to standard output, use
101 for a list of supported debugging formats\&.
|
| /external/dexmaker/src/dx/java/com/android/dx/rop/code/ |
| Rop.java | 76 /** {@code null-ok;} nickname, if specified (used for debugging) */
92 * @param nickname {@code null-ok;} optional nickname (used for debugging)
139 * @param nickname {@code null-ok;} optional nickname (used for debugging)
157 * @param nickname {@code null-ok;} optional nickname (used for debugging)
174 * @param nickname {@code null-ok;} optional nickname (used for debugging)
192 * @param nickname {@code null-ok;} optional nickname (used for debugging)
|
| /external/valgrind/main/none/tests/ |
| cmdline2.stdout.exp | 8 --help-debug show this message, plus debugging options
115 debugging options for all Valgrind tools:
116 -d show verbose debugging output
166 debugging options for Valgrind tools that report errors
170 debugging options for Valgrind tools that replace malloc:
173 debugging options for Nulgrind:
|
| /frameworks/base/docs/html/guide/practices/ |
| verifying-apps-art.jd | 35 href="http://android-developers.blogspot.com/2011/07/debugging-android-jni-with-checkjni.html">Debugging
66 href="{@docRoot}/tools/debugging/debugging-memory.html#LogMessages"><code>GC_FOR_ALLOC</code></a>-type
87 href="http://android-developers.blogspot.com/2011/07/debugging-android-jni-with-checkjni.html">Debugging
|
| /frameworks/base/docs/html/tools/debugging/ |
| debugging-log.jd | 2 parent.title=Debugging
23 <li><a href="#DebuggingWebPages">Debugging Web Pages</a></li>
62 use LogCat within DDMS, see <a href="{@docRoot}tools/debugging/ddms.html#logcat">Using
304 <h2 id="DebuggingWebPages">Debugging Web Apps</h2>
308 <a href="{@docRoot}guide/webapps/debugging.html">Debugging Web Apps</a>.</p>
|
| /frameworks/base/docs/html/tv/adt-1/ |
| index.jd | 80 <strong>Note:</strong> Make sure you have enabled USB debugging in <strong>Settings >
81 Preferences > Developer options > Debugging > USB debugging</strong>, so that you can
104 <strong>Note:</strong> Make sure you have enabled USB debugging in <strong>Settings >
105 Preferences > Developer options > Debugging > USB debugging</strong>, so that you can
|
| /external/chromium_org/build/config/ |
| BUILD.gn | 11 # When set, turns off the (normally-on) iterator debugging and related stuff
154 # Iterator debugging is enabled by the compiler on debug builds, and we
160 # Enable libstdc++ debugging facilities to help catch problems early, see
|
| /external/chromium_org/components/test/data/password_manager/ |
| README | 55 To display the debugging messages on the screen, use:
57 To save debugging messages into a file, use:
169 * If tests fail, isolate the one that causes problem, read debugging messages
|
