Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:debugging (Results 301 - 325 of 6459) sorted by null

<<11121314151617181920>>

/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.8/include/debug/
map	0 // Debugging map/multimap implementation -*- C++ -*-
set	0 // Debugging set/multiset implementation -*- C++ -*-
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.9/include/debug/
map	0 // Debugging map/multimap implementation -*- C++ -*-
set	0 // Debugging set/multiset implementation -*- C++ -*-
/sdk/eclipse/plugins/com.android.ide.eclipse.ndk/src/com/android/ide/eclipse/ndk/internal/launch/
messages.properties	15 NdkGdbLaunchDelegate_LaunchError_Api8Needed=Native debugging requires API level 8 or above.
/external/chromium_org/third_party/yasm/source/patched-yasm/
configure.ac	22 [Turn on debugging and compile time warnings]), 24 yes) debugging="yes" ;; 25 no) debugging="no" ;; 162 # Enable debugging 163 if test "$debugging" != "no"; then 164 debugging=yes 199 if test "$debugging" = "no" ; then
/ndk/sources/host-tools/make-3.81/
make.1	132 Print debugging information in addition to normal processing. 133 The debugging information says which files are being considered for 141 Print debugging information in addition to normal processing. 150 for all debugging output (same as using 153 for basic debugging, 155 for more verbose basic debugging, 161 for debugging while remaking makefiles.
/external/antlr/antlr-3.4/runtime/C/include/
antlr3debugeventlistener.h	3 * The definition of all debugging events that a recognizer can trigger. 7 * I did not create a separate AST debugging interface as it would create 11 * possible events. Hopefully, adding ST debugging stuff won't be bad. Leave 52 /// Default debugging port 60 /** The ANTLR3 debugging interface for communicating with ANLTR Works. Function comments 73 /** The version of the debugging protocol supported by the providing 78 /// The name of the grammar file that we are debugging 98 /// debugging session. 203 * Across a socket for remote debugging, only the RecognitionException 278 * remote debugging listeners that it's time to quit. When the rul     [all...]
antlr3parser.h	67 * installs the debugging versions of the parser methods. This means that 68 * a non debug parser incurs no overhead because of the debugging stuff.
/frameworks/base/docs/html/tools/
device.jd	25 environment and Android-powered device for testing and debugging on the device.</p> 28 debugging, and testing your applications. The tools included in the SDK make it easy to install and 54 <li>Enable debugging over USB.</li> 57 <li>Draw debugging information on screen such as layout bounds, 59 <li>Plus many more options to simulate app stresses or enable debugging options.</li> 78 the Eclipse IDE automatically enables debugging.</p> 81 <p class="note"><strong>Note:</strong> If you manually enable debugging in the manifest 84 <li>Enable <strong>USB debugging</strong> on your device. 140 debugging through this computer. This security mechanism protects user devices because it ensures 141 that USB debugging and other adb commands cannot be executed unless you're able to unlock th     [all...]
/frameworks/base/libs/hwui/
Properties.h	43 // to properly implement overdraw debugging 67 * Used to enable/disable layers update debugging. The accepted values are 73 * Used to enable/disable overdraw debugging. 79 * "false", to disable overdraw debugging 122 * Used to enable/disable non-rectangular clipping debugging.
/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/mdnsresponder/mDNSShared/
DebugServices.h	21 Debugging Library 53 // AssertMacros.h/Debugging.h overrides. 255 kDebugPageFaultFatalMask = 0x00000100, // There should be a "kPageFaultFatalMask" in Debugging.h. 256 kDebugMPTaskLevelMask = 0x00000200, // There should be a "kMPTaskLevelMask" in Debugging.h. 374 @abstract Macro to mark a variable as used only when debugging is enabled. 378 Variables are sometimes needed only for debugging. When debugging is turned off, these debug-only variables generate 380 are only used for debugging. 392 @abstract Macros to make variables and functions static when debugging is off, but extern when debugging is on     [all...]
/external/bison/data/
glr.cc	287 /// The current debugging stream. 289 /// Set the current debugging stream. 292 /// Type for debugging levels. 294 /// The current debugging level. 296 /// Set the current debugging level. 325 /* Debugging. */
/external/chromium_org/native_client_sdk/doc_generated/devguide/devcycle/
vs-addin.html	3 <section id="debugging-with-visual-studio"> 4 <h1 id="debugging-with-visual-studio">Debugging With Visual Studio</h1> 93 ?start debugging? command, Visual Studio automatically launches a web server to 175 module, and to the Chrome browser that you choose to use for debugging.</p> 264 <p>Use the debugging command (F5) to build and run the project. As the wheels 273 <li>&#8220;Debugging information for chrome.exe cannot be found.&#8221; This is to be 274 expected, you are debugging your module&#8217;s code, not Chrome.</li> 284 <li>The Visual Studio output window displays debugging messages when you select 286 Stop the debugging session by closing the Chrome window, or select the sto     [all...]
/frameworks/base/docs/html/tools/help/
proguard.jd	19 <li><a href="#considerations">Debugging considerations for published 90 does not invoke ProGuard, because it makes debugging more cumbersome.</p> 124 <a href="#considerations">Debugging considerations for published applications</a>. 164 debugging hard, if not impossible. Fortunately, whenever ProGuard runs, it outputs a 180 <h3 id="considerations">Debugging considerations for published applications</h3> 192 of debugging the user's stack trace, because the <code>mapping.txt</code> file associated with the version
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/
pipes.py	85 self.debugging = 0 101 t.debugging = self.debugging 105 """t.debug(flag) turns debugging on or off.""" 106 self.debugging = flag 187 if self.debugging:
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/
pipes.py	85 self.debugging = 0 101 t.debugging = self.debugging 105 """t.debug(flag) turns debugging on or off.""" 106 self.debugging = flag 187 if self.debugging:
/external/antlr/antlr-3.4/runtime/Ruby/lib/antlr3/debug/
trace-event-listener.rb	9 Useful for debugging the debugging facility ;)
/external/antlr/antlr-3.4/runtime/Ruby/lib/antlr3/tree/
debug.rb	8 Adds debugging event hooks to TreeAdaptor objects 106 A module that wraps token stream methods with debugging event code. A debuggable
/external/chromium_org/chrome/browser/chromeos/settings/
token_encryptor.cc	39 // Don't care about token encryption while debugging. 54 // Don't care about token encryption while debugging.
/external/chromium_org/native_client_sdk/doc_generated/sdk/
examples.html	151 .nexe files, for ease of debugging. All Debug and Release directories contain 223 </section><section id="debugging-the-sdk-examples"> 224 <span id="id2"></span><h2 id="debugging-the-sdk-examples"><span id="id2"></span>Debugging the SDK examples</h2> 242 Remote debugging using :4014 247 <code>next</code>, <code>break</code> and <code>backtrace</code>. See <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>Debugging</em></a> for more information about debugging a Native Client
/external/chromium_org/remoting/base/
auto_thread.h	54 // Construct the AutoThread. |name| identifies the thread for debugging. 100 // The name of the thread. Used for debugging purposes.
/external/chromium_org/third_party/freetype/include/freetype/internal/
ftdebug.h	5 /* Debugging and logging component (specification). */ 17 /* IMPORTANT: A description of FreeType's debugging support can be */
/external/chromium_org/third_party/icu/source/test/intltest/
normconf.h	37 // Specific tests for debugging. These are generally failures taken from 38 // the conformance file, but culled out to make debugging easier.

Completed in 732 milliseconds

<<11121314151617181920>>