blob: bdc820d87ffd155b9c1ca1c4a98acb15060c3972 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
page.title=dmtracedump
parent.title=Tools
parent.link=index.html
@jd:body
<p><code>dmtracedump</code> is a tool that gives you an alternate way of generating
graphical call-stack diagrams from trace log files (instead of using Traceview).</p>
<p>This document is a reference to the available command line options. For more information on generating trace
logs, see <a href="{@docRoot}tools/debugging/debugging-tracing.html">Profiling with
Traceview and dmtracedump</a>.</p>
<p>The usage for <code>dmtracedump</code> is:</p>
<pre>
dmtracedump [-ho] [-s sortable] [-d trace-base-name] [-g outfile] <trace-base-name>
</pre>
<p>The tool then loads trace log data from <code><trace-base-name>.data</code> and
<trace-base-name>.key. The table below lists the options for dmtracedump.</p>
<table>
<tr>
<th>Option</th>
<th>Description</th>
</tr>
<tr>
<td><nobr><code>-d <em><trace-base-name></em></code></nobr></td>
<td>Diff with this trace name</td>
</tr>
<tr>
<td><code>-g <em><outfile></em></code></td>
<td>Generate output to <outfile></td>
</tr>
<tr>
<td><code>-h</code></td>
<td>Turn on HTML output</td>
</tr>
<tr>
<td><code>-o</code></td>
<td>Dump the trace file instead of profiling</td>
</tr>
<tr>
<td><code>-d <em><trace-base-name></em></code></td>
<td>URL base to the location of the sortable javascript file</td>
</tr>
<tr>
<td><code>-t <percent></code></td>
<td>Minimum threshold for including child nodes in the graph (child's inclusive time as a
percentage of parent inclusive time). If this option is not used, the default threshold is
20%.</td>
</tr>
</table>
|