/frameworks/support/v4/java/android/support/v4/util/ |
TimeUtils.java | 143 /** @hide Just for debugging; not internationalized. */ 151 /** @hide Just for debugging; not internationalized. */ 159 /** @hide Just for debugging; not internationalized. */ 164 /** @hide Just for debugging; not internationalized. */
|
/ndk/sources/host-tools/ndk-stack/elff/ |
elff_api.cc | 15 * an ELF file containing debugging information in DWARF format.
|
/packages/providers/CalendarProvider/src/com/android/providers/calendar/ |
CalendarDebugReceiver.java | 31 * displays debugging information.
|
/prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/i686-linux/include/c++/4.4.3/debug/ |
map | 0 // Debugging map/multimap implementation -*- C++ -*-
|
set | 0 // Debugging set/multiset implementation -*- C++ -*-
|
/prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/ |
flat.h | 54 #define FLAT_FLAG_KTRACE 0x0010 /* output useful kernel trace for debugging */
|
if_tun.h | 21 /* Uncomment to enable debugging */
|
/prebuilt/ndk/android-ndk-r5/sources/cxx-stl/gnu-libstdc++/include/debug/ |
map | 0 // Debugging map/multimap implementation -*- C++ -*-
|
set | 0 // Debugging set/multiset implementation -*- C++ -*-
|
/prebuilt/ndk/android-ndk-r6/sources/cxx-stl/gnu-libstdc++/include/debug/ |
map | 0 // Debugging map/multimap implementation -*- C++ -*-
|
set | 0 // Debugging set/multiset implementation -*- C++ -*-
|
/external/llvm/docs/ |
DebuggingJITedCode.html | 5 <title>Debugging JITed Code With GDB</title> 10 <h1>Debugging JITed Code With GDB</h1> 25 option for debugging JITed code on Mac OS X. 28 <p>Consider debugging the following code compiled with clang and run through 72 [Thread debugging using libthread_db enabled] 103 <p>Without special runtime support, debugging dynamically generated code with 109 <p>Depending on the architecture, this can impact the debugging experience in
|
/external/chromium/chrome/browser/task_manager/ |
task_manager_browsertest.cc | 121 // Show the task manager. This populates the model, and helps with debugging 151 // Show the task manager. This populates the model, and helps with debugging 179 // Show the task manager. This populates the model, and helps with debugging 218 // Show the task manager. This populates the model, and helps with debugging 237 // Show the task manager. This populates the model, and helps with debugging 276 // Show the task manager. This populates the model, and helps with debugging 342 // Show the task manager. This populates the model, and helps with debugging 365 // Show the task manager. This populates the model, and helps with debugging 400 // Show the task manager. This populates the model, and helps with debugging 444 // Show the task manager. This populates the model, and helps with debugging [all...] |
/frameworks/base/services/java/com/android/server/am/ |
ProcessRecord.java | 99 String adjType; // Debugging: primary thing impacting oom_adj. 100 int adjTypeCode; // Debugging: adj code to report to app. 101 Object adjSource; // Debugging: option dependent object. 102 int adjSourceOom; // Debugging: oom_adj of adjSource's process. 103 Object adjTarget; // Debugging: target component impacting oom_adj. 130 boolean debugging; // was app launched for debugging? field in class:ProcessRecord 228 if (debugging || crashing || crashDialog != null || notResponding 230 pw.print(prefix); pw.print("debugging="); pw.print(debugging); [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. 105 <refsect1 id="debugging-valgrind-options"> 106 <title>Debugging Valgrind Options</title>
|
/external/wpa_supplicant_8/hostapd/ |
defconfig | 136 # Remove debugging code that is printing out debug messages to stdout. 137 # This can be used to reduce the size of the hostapd considerably if debugging 159 # This can be used to reduce binary size at the cost of disabling a debugging 163 # Enable tracing code for developer debugging 172 # Use libbfd to get more details for developer debugging
|
/external/llvm/lib/Analysis/ |
DIBuilder.cpp | 34 /// createCompileUnit - A CompileUnit provides an anchor for all debugging 60 /// createFile - Create a file descriptor to hold debugging information 83 /// createBasicType - Create debugging information entry for a basic 105 /// createQaulifiedType - Create debugging information entry for a qualified 124 /// createPointerType - Create debugging information entry for a pointer. 143 /// createReferenceType - Create debugging information entry for a reference. 161 /// createTypedef - Create debugging information entry for a typedef. 181 /// createFriend - Create debugging information entry for a 'friend'. 201 /// createInheritance - Create debugging information entry to establish 221 /// createMemberType - Create debugging information entry for a member [all...] |
/dalvik/docs/ |
debugger.html | 10 The Dalvik virtual machine supports source-level debugging with many popular 11 development environments. Any tool that allows remote debugging over JDWP 38 Every VM that has debugging enabled starts a "JDWP" thread. The thread 44 When the VM is started from the Android app framework, debugging is enabled 47 to check it). If it's zero, debugging can be enabled via the application's 85 when debugging support is enabled. 98 desktop VMs do. To start a VM with debugging enabled, you add a command-line 156 This tells the Dalvik VM to run the program with debugging enabled, listening 174 more convenient when debugging on an Android device, but when working with
|
/external/bluetooth/glib/docs/reference/glib/tmpl/ |
testing.sgml | 404 Debugging macro to terminate the application if the assertion fails. 418 Debugging macro to terminate the application if it is ever reached. 430 Debugging macro to terminate the application with a warning message 452 Debugging macro to terminate the application with a warning message 470 Debugging macro to terminate the application with a warning message 488 Debugging macro to terminate the application with a warning message 502 Debugging macro to terminate the application with a warning message 520 Debugging macro to terminate the application with a warning message 535 Debugging macro to terminate the application with a warning message
|
/external/bison/data/ |
glr.cc | 320 /// The current debugging stream. 322 /// Set the current debugging stream. 325 /// Type for debugging levels. 327 /// The current debugging level. 329 /// Set the current debugging level. 371 /* Debugging. */
|
/external/valgrind/main/none/tests/ |
cmdline2.stdout.exp | 8 --help-debug show this message, plus debugging options 73 debugging options for all Valgrind tools: 74 -d show verbose debugging output 114 debugging options for Valgrind tools that report errors 118 debugging options for Valgrind tools that replace malloc: 121 debugging options for Nulgrind:
|
/frameworks/base/docs/html/guide/developing/tools/ |
proguard.jd | 19 <li><a href="#considerations">Debugging considerations for published 81 does not invoke ProGuard, because it makes debugging more cumbersome.</p> 115 <a href="#considerations">Debugging considerations for published applications</a>. 155 debugging hard, if not impossible. Fortunately, whenever ProGuard runs, it outputs a 171 <h3 id="considerations">Debugging considerations for published applications</h3> 183 of debugging the user's stack trace, because the <code>mapping.txt</code> file associated with the version
|
/cts/tests/tests/view/src/android/view/cts/ |
ViewDebugTest.java | 67 // debugging should be disabled on production devices 105 // debugging should be disabled on production devices
|
/dalvik/vm/ |
LinearAlloc.h | 64 * erased to aid debugging. 97 * may be erased to aid debugging.
|
/dalvik/vm/analysis/ |
VerifySubs.cpp | 26 * This is used when debugging to apply a magnifying glass to the 31 return false; /* COMMENT OUT to enable verbose debugging */
|