| /frameworks/base/cmds/uiautomator/library/core-src/com/android/uiautomator/core/ |
| D | UiDevice.java | 129 Tracer.trace(); in getDisplaySizeDp()
152 Tracer.trace(); in getProductName()
172 Tracer.trace(); in getLastTraversedText()
182 Tracer.trace(); in clearLastTraversedText()
192 Tracer.trace(); in pressMenu()
205 Tracer.trace(); in pressBack()
218 Tracer.trace(); in pressHome()
231 Tracer.trace(); in pressSearch()
241 Tracer.trace(); in pressDPadCenter()
251 Tracer.trace(); in pressDPadDown()
[all …]
|
| D | UiScrollable.java | 66 Tracer.trace(); in setAsVerticalList()
77 Tracer.trace(); in setAsHorizontalList()
117 Tracer.trace(childPattern, text); in getChildByDescription()
139 Tracer.trace(childPattern, text, allowScrollSearch); in getChildByDescription()
163 Tracer.trace(childPattern, instance); in getChildByInstance()
188 Tracer.trace(childPattern, text); in getChildByText()
209 Tracer.trace(childPattern, text, allowScrollSearch); in getChildByText()
229 Tracer.trace(text); in scrollDescriptionIntoView()
242 Tracer.trace(obj.getSelector()); in scrollIntoView()
257 Tracer.trace(selector); in scrollIntoView()
[all …]
|
| D | UiObject.java | 89 Tracer.trace(); in getSelector()
121 Tracer.trace(selector); in getChild()
135 Tracer.trace(selector); in getFromParent()
147 Tracer.trace(); in getChildCount()
238 Tracer.trace(steps); in swipeUp()
266 Tracer.trace(steps); in swipeDown()
294 Tracer.trace(steps); in swipeLeft()
321 Tracer.trace(steps); in swipeRight()
393 Tracer.trace(); in click()
413 Tracer.trace(); in clickAndWaitForNewWindow()
[all …]
|
| D | UiCollection.java | 52 Tracer.trace(childPattern, text); in getChildByDescription()
86 Tracer.trace(childPattern, instance); in getChildByInstance()
110 Tracer.trace(childPattern, text); in getChildByText()
140 Tracer.trace(childPattern); in getChildCount()
|
| D | Tracer.java | 209 public static void trace(Object... arguments) { in trace() method in Tracer
|
| /frameworks/base/docs/html/tools/help/ |
| D | dmtracedump.jd | 8 graphical call-stack diagrams from trace log files (instead of using Traceview).</p>
10 …ment is a reference to the available command line options. For more information on generating trace
16 dmtracedump [-ho] [-s sortable] [-d trace-base-name] [-g outfile] <trace-base-name>
19 <p>The tool then loads trace log data from <code><trace-base-name>.data</code> and
20 <trace-base-name>.key. The table below lists the options for dmtracedump.</p>
30 <td><nobr><code>-d <em><trace-base-name></em></code></nobr></td>
32 <td>Diff with this trace name</td>
50 <td>Dump the trace file instead of profiling</td>
54 <td><code>-d <em><trace-base-name></em></code></td>
|
| D | gltracer.jd | 55 16) or higher that is running the application you want to analyze. The Tracer tool captures trace
59 <img src="{@docRoot}images/gltracer/dialog-trace.png">
62 <p>To capture an OpenGL ES trace for an Android application:</p>
69 <li>On the toolbar, click the trace capture button (<img
71 <li>In the dialog box, select the <strong>Device</strong> to use for the trace.</li>
73 containing the activity you want to trace, for example: {@code com.example.android.opengl}</li>
75 want to trace, for example: {@code OpenGLES20Complete}
82 Be aware that using this option can result in large trace files.</p>
84 <li>Enter a <strong>Destination File</strong> for the trace output.</li>
85 <li>Click <strong>Trace</strong> to start the trace capture.</li>
[all …]
|
| D | systrace.jd | 22 computer's execution path. In order to generate a trace, you must connect a device running Android
50 <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no
55 <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li>
71 <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no
76 <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li>
90 <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no
95 <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li>
118 <p>When you use Systrace on devices running Android 4.3 and higher, you can omit trace category tags
120 run that sets trace tags and generates a trace from a connected device.</p>
128 <strong>Tip:</strong> If you want to see the names of tasks in the trace output, you <em>must</em>
[all …]
|
| D | proguard.jd | 164 translates the obfuscated stack trace back to the original class, method, and member names.
226 <p>When your obfuscated code outputs a stack trace, the method names are obfuscated, which makes
232 or Mac OS X can convert an obfuscated stack trace to a readable one. It is located
247 …sure that you can debug a problem if a user encounters a bug and submits an obfuscated stack trace.
256 …containing a stack trace from the application that is currently published. You no longer have a way
257 …of debugging the user's stack trace, because the <code>mapping.txt</code> file associated with the…
|
| /frameworks/base/docs/html/tools/debugging/ |
| D | debugging-tracing.jd | 40 …<p>When you have a trace log file (generated by adding tracing code to your application or by DDMS…
89 <p>To use Traceview, you need to generate log files containing the trace information you want to
92 <p>There are two ways to generate trace logs:</p>
96 android.os.Debug#stopMethodTracing()}, to start and stop logging of trace information to disk.
98 you can specify exactly where to start and stop logging trace data in your code.</li>
99 <li>Use the method profiling feature of DDMS to generate trace logs. This option is less
107 <p>Before you start generating trace logs, be aware of the following restrictions:</p>
116 <li>Android 2.2 and later devices do not need an SD card. The trace log files are
122 …<p>This document focuses on using the {@link android.os.Debug} class to generate trace data. For …
123 …to generate trace data, see <a href="ddms.html#profiling">Using the Dalvik Debug Monitor Server.</…
[all …]
|
| D | systrace.jd | 19 <li><a href="#app-trace">Tracing Application Code</a></li>
33 device, which is called a <em>trace</em>. It shows where time and CPU cycles are being spent,
37 the trace files produced by the tool, and use them to analyze the performance of an application's
44 timeline. In order to analyze your app with Systrace, you first collect a trace log of your app, and
45 the system activity. The generated trace allows you to view highly detailed, interactive reports
54 <p>Figure 1. shows a trace captured while scrolling an app that is not rendering smoothly. By
55 default, a zoomed out view of the traced duration is shown. The horizontal axis is time, and trace
66 <p>In order to create a trace of your application, you must perform a few setup steps. First, you
69 system, and install your application. Some types of trace information, specifically disk activity
80 <p>To run a trace on Android 4.3 and higher devices:</p>
[all …]
|
| D | index.jd | 103 <dd>A graphical viewer that displays trace file data for method calls and times saved by your
121 <dt><strong>Dump the stack trace</strong></dt>
124 want, and then <code>kill -3</code>. The stack trace appears in the log file.
144 <dt><strong>Log trace data</strong></dt>
|
| /frameworks/base/core/java/android/ddm/ |
| D | DdmHandleThread.java | 131 StackTraceElement[] trace = DdmVmInternal.getStackTraceById(threadId); in handleSTKL() local
132 if (trace == null) { in handleSTKL()
135 return createStackChunk(trace, threadId); in handleSTKL()
145 private Chunk createStackChunk(StackTraceElement[] trace, int threadId) { in createStackChunk() argument
151 for (StackTraceElement elem : trace) { in createStackChunk()
163 out.putInt(trace.length); in createStackChunk()
164 for (StackTraceElement elem : trace) { in createStackChunk()
|
| /frameworks/native/opengl/libs/GLES_trace/ |
| D | DESIGN.txt | 8 enabled. Currently, the shell properties "debug.egl.trace" and "debug.egl.debug_proc" together
10 calls GLTrace_start() to start the trace server.
13 specific gl_hooks structure to point to the trace implementation. From this point on, every
14 GLES call is redirected to the trace implementation.
19 trace implementation.
21 For EGL calls, the trace library provides a bunch of functions that must be explicitly called
35 real GL implementation, and we need to switch them to point to the trace implementation.
42 - switch the gl hooks to point to the trace implementation.
43 - call trace eglMakeCurrent to indicate that there is now a new context that is current.
45 This switches the hooks to point to the trace implementation only for the current context.
[all …]
|
| /frameworks/volley/src/main/java/com/android/volley/ |
| D | VolleyLog.java | 85 StackTraceElement[] trace = new Throwable().fillInStackTrace().getStackTrace(); in buildMessage() local
90 for (int i = 2; i < trace.length; i++) { in buildMessage()
91 Class<?> clazz = trace[i].getClass(); in buildMessage()
93 String callingClass = trace[i].getClassName(); in buildMessage()
97 caller = callingClass + "." + trace[i].getMethodName(); in buildMessage()
|
| /frameworks/native/include/ui/ |
| D | TMatHelpers.h | 55 inline int PURE trace(int v) { return v; } in trace() function
56 inline float PURE trace(float v) { return v; } in trace() function
57 inline double PURE trace(double v) { return v; } in trace() function
142 typename MATRIX::value_type PURE trace(const MATRIX& m) { in trace() function
146 result += trace(m[r][r]); in trace()
241 friend T PURE trace(const BASE<T>& m) { return matrix::trace(m); } in trace() function
|
| /frameworks/base/docs/html/tools/performance/systrace/ |
| D | index.jd | 131 <strong>Figure 3. </strong>Steps for creating a trace.
135 <li>In the <b>Android System Trace</b> popup, choose your settings for the trace.
138 <li><b>Destination File:</b> Where the trace is stored as an HTML file. Default is in
139 your home directory as <code>trace.html</code>.</li>
148 <li><b>Select tags to enable:</b> Choose at least one value to trace, for example Graphics
172 <li>When the trace is done, you are automatically returned to Android Device Monitor.</li>
176 <li>Open the <code>trace.html</code> file in your browser.</li>
|
| /frameworks/base/core/java/android/app/ |
| D | ApplicationErrorReport.java | 366 StackTraceElement trace = rootTr.getStackTrace()[0]; in CrashInfo() local
367 throwFileName = trace.getFileName(); in CrashInfo()
368 throwClassName = trace.getClassName(); in CrashInfo()
369 throwMethodName = trace.getMethodName(); in CrashInfo()
370 throwLineNumber = trace.getLineNumber(); in CrashInfo()
|
| /frameworks/base/native/android/ |
| D | Android.mk | 19 trace.cpp \
|
| /frameworks/native/opengl/libs/ |
| D | Android.mk | 30 EGL/trace.cpp \
|
| /frameworks/native/opengl/libs/tools/ |
| D | genfiles | 43 ./gltracegen ../entries.in >../trace.in
|
| /frameworks/base/core/java/com/android/internal/os/ |
| D | RuntimeInit.java | 150 String trace = SystemProperties.get("ro.kernel.android.tracing"); in commonInit() local
151 if (trace.equals("1")) { in commonInit()
|
| /frameworks/native/libs/ui/tests/ |
| D | mat_test.cpp | 113 EXPECT_EQ(4, trace(m0)); in TEST_F()
|
| /frameworks/compile/mclinker/lib/Core/ |
| D | Linker.cpp | 106 if (m_pConfig->options().trace()) { in normalize()
|
| /frameworks/wilhelm/src/ |
| D | Android.mk | 78 trace.c \
|