Home | History | Annotate | Download | only in debugging

Lines Matching full:trace

21         <li><a href="#creatingtracefiles">Creating Trace Files</a></li>
23 <li><a href="#copyingfiles">Copying Trace Files to a Host Machine</a></li>
25 <li><a href="#runningtraceview">Viewing Trace Files in Traceview</a></li>
40 <p>When you have a trace log file (generated by adding tracing code to your application or by DDMS),
89 <h2 id="creatingtracefiles">Creating Trace Files</h2>
91 <p>To use Traceview, you need to generate log files containing the trace information you want to
94 <p>There are two ways to generate trace logs:</p>
97 methods to start and stop logging of trace information to disk. This method is very precise because
98 you can specify in your code exactly where to start and stop logging trace data.</li>
99 <li>Use the method profiling feature of DDMS to generate trace logs. This method is less
106 <p>Before you start generating trace logs, be aware of the following restrictions:</p>
112 <li>If you are using DDMS, Android 2.2 and later devices do not need an SD card. The trace log files are
116 <p>This document focuses on using the {@link android.os.Debug} class to generate trace data. For more information on using DDMS
117 to generate trace data, see <a href="ddms.html#profiling">Using the Dalvik Debug Monitor Server.</a>
120 <p>To create the trace files, include the {@link android.os.Debug} class and call one of the
122 specify a base name for the trace files that the system generates. To stop tracing, call {@link
130 // start tracing to "/sdcard/calc.trace"
138 <code>&lt;trace-base-name&gt;.trace</code>. This contains the binary method trace data and a
141 <p>The system then begins buffering the generated trace data, until your application calls
151 <p>When using the Android emulator, you must specify an SD card when you create your AVD because the trace files
154 <h2 id="copyingfiles">Copying Trace Files to a Host Machine</h2>
156 <p>After your application has run and the system has created your trace files
157 <code>&lt;trace-base-name&gt;.trace</code> on a device or emulator, you must copy those files to
159 that shows how to copy an example file, calc.trace, from the default location on the emulator to
162 adb pull /sdcard/calc.trace /tmp
165 <h2 id="runningtraceview">Viewing Trace Files in Traceview</h2>
167 <p>To run Traceview and view the trace files, enter <code>traceview
168 &lt;trace-base-name&gt;</code>. For example, to run Traceview on the example files copied in the
174 <p class="note"><strong>Note:</strong> If you are trying to view the trace logs of an application
182 graphical call-stack diagrams from trace log files. The tool uses the Graphviz Dot utility to
198 <li><code>&lt;ref&gt;</code> -- Call reference number, as used in trace logs</li>
211 dmtracedump [-ho] [-s sortable] [-d trace-base-name] [-g outfile] &lt;trace-base-name&gt;
214 <p>The tool then loads trace log data from <code>&lt;trace-base-name&gt;.data</code> and
215 <code>&lt;trace-base-name&gt;.key</code>. The table below lists the options for dmtracedump.</p>
225 <td><code>-d&nbsp;&lt;trace-base-name&gt;</code></td>
227 <td>Diff with this trace name</td>
245 <td>Dump the trace file instead of profiling</td>
249 <td><code>-d&nbsp;&lt;trace-base-name&gt;</code></td>