/frameworks/base/docs/html/tools/debugging/ |
D | index.jd | 25 comprise a typical Android debugging environment are:</p> 35 <dt><a href="{@docRoot}tools/debugging/ddms.html"><strong>Dalvik Debug Monitor 54 tedious, so DDMS provides a port forwarding feature that can forward a specific VM's debugging 63 <p>Figure 1 shows how the various debugging tools work together in a typical 64 debugging environment.</p> 65 <img src="{@docRoot}images/debugging.png" 77 <p>Each application VM on the device or emulator exposes a debugging port that you can attach to 78 via DDMS. DDMS can forward any of these ports to a static debugging port (typically port 8700) by 80 attach to this static debugging port and debug all the applications that are running on the 90 <p>In addition to the main debugging tools, the Android SDK provides additional tools to help you [all …]
|
D | debugging-projects-cmdline.jd | 12 <li><a href="#start-debugging">Starting a Debugging Environment</a> 22 the Android SDK provides for debugging. A basic debugging environment consists of:</p> 27 <li><a href="{@docRoot}tools/debugging/ddms.html">DDMS</a></li> 36 <h2 id="start-debugging">Starting a debugging environment</h2> 39 variable values. Since you are not using Eclipse, you have to manually start up the debugging 41 debugging your application, follow these general steps:</p> 52 <li>Attach your debugger to the debugging port 8700, or to the specific port shown for the 58 <p>DDMS assigns a specific debugging port to every virtual machine that it finds on the
|
D | ddms.jd | 31 <p>Android ships with a debugging tool called the Dalvik Debug Monitor Server (DDMS), which 61 <p>DDMS assigns a debugging port to each VM on the device. Typically, 67 …<p>By default, DDMS also listens on another debugging port, the DDMS "base port" (8700, by default… 68 The base port is a port forwarder, which can accept VM traffic from any debugging port and forward 76 has the debugging port 8700 assigned to it as well as 8606. This signifies that DDMS is currently 77 forwarding port 8606 to the static debugging port of 8700.</p> 85 "{@docRoot}tools/debugging/debugging-projects-cmdline.html#debuggingPort">Configuring 86 your IDE to attach to the debugging port</a>, for more information on attaching your 93 <p class="warning"><strong>Known debugging issues with Dalvik</strong><br /> 191 <a href="debugging-tracing.html">Profiling and Debugging UIs</a>.</p> [all …]
|
D | debugging-devtools.jd | 27 time while debugging.</li> 71 happen, but can happen during debugging.</dd>
|
/frameworks/base/docs/html/tools/help/ |
D | monitor.jd | 9 <li><a href="{@docRoot}tools/debugging/debugging-memory.html" 17 several Android application debugging and analysis tools. The Monitor tool does not 22 <li><a href="{@docRoot}tools/debugging/ddms.html">DDMS</a></li> 40 If you're using ADT, you may need to close the debugging tool before launching the Device Monitor
|
D | logcat.jd | 12 <a href="{@docRoot}tools/debugging/debugging-log.html">Reading and Writing Logs</a>.</p> 15 <a href="{@docRoot}tools/debugging/ddms.html">Using DDMS</a>. </p> 50 …"{@docRoot}tools/debugging/debugging-log.html#alternativeBuffers">Viewing Alternative Log Buffers<… 102 …list of supported formats, see <a href="{@docRoot}tools/debugging/debugging-log.html#outputFormat"…
|
D | traceview.jd | 14 <a href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with Traceview and dmtracedump…
|
D | hierarchy-viewer.jd | 16 <a href="{@docRoot}tools/debugging/debugging-ui.html">Debugging and Profiling UIs</a>
|
D | layoutopt.jd | 11 href="{@docRoot}tools/debugging/debugging-ui.html#layoutopt">Optimizing layouts with
|
D | dmtracedump.jd | 11 logs, see <a href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with
|
D | index.jd | 21 <dt><a href="{@docRoot}tools/debugging/ddms.html">Dalvik Debug Monitor 28 href="{@docRoot}tools/debugging/debugging-tracing.html#dmtracedump">Profiling
|
D | 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
|
D | proguard.jd | 81 does not invoke ProGuard, because it makes debugging more cumbersome.</p> 155 debugging hard, if not impossible. Fortunately, whenever ProGuard runs, it outputs a 183 …of debugging the user's stack trace, because the <code>mapping.txt</code> file associated with the…
|
D | systrace.jd | 15 on how to use {@code systrace}, see <a href="{@docRoot}tools/debugging/systrace.html">Analyzing 24 4.1 (API Level 16) or higher to your development system using a USB debugging connection.</p>
|
/frameworks/base/docs/html/tools/ |
D | index.jd | 50 <li>Enable debugging over USB.</li> 53 <li>Draw debugging information on screen such as layout bounds, 55 <li>Plus many more options to simulate app stresses or enable debugging options.</li> 76 <li>Live, on-device debugging, testing, and profiling.</li> 96 <li>Full Java debugger with on-device debugging and Android-specific tools.</li> 98 …<li>Graphical tools for debugging and optimizing UI, runtime inspecton of UI structure and perform… 119 <img src="{@docRoot}images/debugging-tall.png" align="left" style="margin-top:10px">
|
D | device.jd | 24 environment and Android-powered device for testing and debugging on the device.</p> 27 debugging, and testing your applications. The tools included in the SDK make it easy to install and 55 the Eclipse IDE automatically enables debugging.</p> 58 <p class="note"><strong>Note:</strong> If you manually enable debugging in the manifest 61 <li>Enable <strong>USB debugging</strong> on your device. 117 debugging through this computer. This security mechanism protects user devices because it ensures 118 that USB debugging and other adb commands cannot be executed unless you're able to unlock the
|
D | workflow.jd | 47 <p>Next, you debug your application using a JDWP-compliant debugger along with the debugging 50 <a href="{@docRoot}tools/debugging/index.html">Debug your application with the 51 SDK debugging and logging tools</a>.</p>
|
/frameworks/base/docs/html/guide/webapps/ |
D | debugging.jd | 9 <li>If debugging in a custom WebView, you need to implement a callback method to handle debug 21 <li><a href="{@docRoot}tools/debugging/index.html">Debugging</a></li> 29 debugging web pages with Firebug or Web Inspector, then you're probably familiar 31 of the same APIs, so you can receive logs from your web page when debugging in Android's Browser 49 <p>See <a href="{@docRoot}tools/debugging/debugging-log.html">Debugging</a> 87 same console APIs are supported when debugging your web page in WebView. On Android
|
/frameworks/base/docs/html/tools/workflow/ |
D | index.jd | 47 <p>Next, you debug your application using a JDWP-compliant debugger along with the debugging 50 <a href="{@docRoot}tools/debugging/index.html">Debug your application with the 51 SDK debugging and logging tools</a>.</p>
|
/frameworks/compile/slang/lit-tests/ |
D | README | 18 When debugging failures, the "-v" option will print to stdout the details of
|
/frameworks/base/docs/html/training/articles/ |
D | memory.jd | 43 <li><a href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a> 68 href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a>.</p> 111 href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a>.</p> 128 href="{@docRoot}tools/debugging/debugging-memory.html#ViewingAllocations">Investigating Your 473 <p>You should also read about <a href="{@docRoot}tools/debugging/debugging-ui.html">optimizing 474 your UI</a> with the layout debugging tools and take advantage of 476 href="{@docRoot}tools/debugging/improving-w-lint.html">lint tool</a>.</p> 503 href="{@docRoot}tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a>.</p> 565 in <a href="{@docRoot}tools/debugging/debugging-memory.html#ViewingAllocations">Investigating
|
D | perf-tips.jd | 419 <a href="{@docRoot}tools/debugging/debugging-tracing.html">Traceview</a> useful 426 <p>For more help profiling and debugging your apps, see the following documents:</p> 429 <li><a href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with 431 <li><a href="{@docRoot}tools/debugging/systrace.html">Analysing Display and Performance
|
/frameworks/base/docs/html/sdk/ |
D | exploring.jd | 25 <td>Contains tools for debugging and testing, plus other 30 <td>Contains platform-dependent tools for developing and debugging 61 stepping through the code while debugging your app.</td>
|
/frameworks/base/docs/html/sdk/installing/ |
D | studio-tips.jd | 115 you can find the complete set of <a href="{@docRoot}tools/debugging/ddms.html">DDMS</a> 118 <a href="{@docRoot}tools/debugging/debugging-ui.html">optimize your layouts</a>.</p>
|
/frameworks/base/services/java/com/android/server/am/ |
D | ProcessRecord.java | 156 boolean debugging; // was app launched for debugging? field in ProcessRecord 297 if (debugging || crashing || crashDialog != null || notResponding in dump() 299 pw.print(prefix); pw.print("debugging="); pw.print(debugging); in dump()
|