Home
last modified time | relevance | path

Searched refs:trace (Results 1 – 25 of 40) sorted by relevance

12

/frameworks/base/docs/html/guide/developing/tools/
Ddmtracedump.jd8 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] &lt;trace-base-name&gt;
19 <p>The tool then loads trace log data from <code>&lt;trace-base-name&gt;.data</code> and
20 &lt;trace-base-name&gt;.key. The table below lists the options for dmtracedump.</p>
30 <td><nobr><code>-d&nbsp;<em>&lt;trace-base-name&gt;</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&nbsp;<em>&lt;trace-base-name&gt;</em></code></td>
Dproguard.jd92 translates the obfuscated stack trace back to the original class, method, and member names.
154 <p>When your obfuscated code outputs a stack trace, the method names are obfuscated, which makes
160 or Mac OS X can convert an obfuscated stack trace to a readable one. It is located in the
175 …sure that you can debug a problem if a user encounters a bug and submits an obfuscated stack trace.
182 …containing a stack trace from the application that is currently published. You no longer have a wa…
183 …of debugging the user's stack trace, because the <code>mapping.txt</code> file associated with the…
Dindex.jd26 <dd>Generates graphical call-stack diagrams from trace log files. The tool uses the
/frameworks/base/core/java/com/android/internal/http/multipart/
DPart.java204 LOG.trace("enter sendStart(OutputStream out)"); in sendStart()
217 LOG.trace("enter sendDispositionHeader(OutputStream out)"); in sendDispositionHeader()
230 LOG.trace("enter sendContentTypeHeader(OutputStream out)"); in sendContentTypeHeader()
252 LOG.trace("enter sendTransferEncodingHeader(OutputStream out)"); in sendTransferEncodingHeader()
267 LOG.trace("enter sendEndOfHeader(OutputStream out)"); in sendEndOfHeader()
293 LOG.trace("enter sendEnd(OutputStream out)"); in sendEnd()
306 LOG.trace("enter send(OutputStream out)"); in send()
326 LOG.trace("enter length()"); in length()
419 LOG.trace("getLengthOfParts(Parts[])"); in getLengthOfParts()
DFilePart.java191 LOG.trace("enter sendDispositionHeader(OutputStream out)"); in sendDispositionHeader()
210 LOG.trace("enter sendData(OutputStream out)"); in sendData()
239 LOG.trace("enter getSource()"); in getSource()
250 LOG.trace("enter lengthOfData()"); in lengthOfData()
DStringPart.java126 LOG.trace("enter sendData(OutputStream)"); in sendData()
137 LOG.trace("enter lengthOfData()"); in lengthOfData()
/frameworks/base/core/java/android/ddm/
DDdmHandleThread.java131 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/base/docs/html/guide/developing/debugging/
Ddebugging-tracing.jd49 …<p>When you have a trace log file (generated by adding tracing code to your application or by DDMS…
100 <p>Tracing creates two distinct pieces of output: a <em>data</em> file, which holds the trace
102 method names. The files are concatenated when tracing completes, into a single <em>.trace</em>
106 these files for you. If you have old key and data files that you'd still like to trace, you can
108 mytrace.trace</code>.</p>
208 <p>To use Traceview, you need to generate log files containing the trace information you want to
211 <p>There are two ways to generate trace logs:</p>
214 …methods to start and stop logging of trace information to disk. This method is very precise because
215 you can specify in your code exactly where to start and stop logging trace data.</li>
216 <li>Use the method profiling feature of DDMS to generate trace logs. This method is less
[all …]
Dindex.jd102 <dd>A graphical viewer that displays trace file data for method calls and times saved by your
120 <dt><strong>Dump the stack trace</strong></dt>
123 want, and then <code>kill -3</code>. The stack trace appears in the log file.
145 <dt><strong>Log trace data</strong></dt>
Dddms.jd180 …{@link android.os.Debug#stopMethodTracing()} methods. For more information about generating trace
188 <li>Android 2.2 and later devices do not need an SD card. The trace log files are
/frameworks/base/core/java/android/app/
DApplicationErrorReport.java349 StackTraceElement trace = rootTr.getStackTrace()[0]; in CrashInfo() local
350 throwFileName = trace.getFileName(); in CrashInfo()
351 throwClassName = trace.getClassName(); in CrashInfo()
352 throwMethodName = trace.getMethodName(); in CrashInfo()
353 throwLineNumber = trace.getLineNumber(); in CrashInfo()
/frameworks/base/test-runner/src/junit/runner/
DTestRunListener.java19 public void testFailed(int status, String testName, String trace); in testFailed() argument
DBaseTestRunner.java269 String trace= buffer.toString(); in getFilteredTrace() local
270 return BaseTestRunner.getFilteredTrace(trace); in getFilteredTrace()
/frameworks/base/opengl/libs/
DAndroid.mk15 EGL/trace.cpp \
/frameworks/base/core/java/android/view/
DViewDebug.java670 public static void trace(View view, RecyclerTraceType type, int... parameters) { in trace() method in ViewDebug
681 RecyclerTrace trace = new RecyclerTrace(); in trace() local
682 trace.view = index; in trace()
683 trace.type = type; in trace()
684 trace.position = parameters[0]; in trace()
685 trace.indexOnScreen = parameters[1]; in trace()
687 sRecyclerTraces.add(trace); in trace()
782 for (RecyclerTrace trace : sRecyclerTraces) { in stopRecyclerTracing()
783 out.writeInt(trace.view); in stopRecyclerTracing()
784 out.writeInt(trace.type.ordinal()); in stopRecyclerTracing()
[all …]
/frameworks/base/opengl/libs/tools/
Dgenfiles35 ./gltracegen ../entries.in >../trace.in
/frameworks/base/tests/CoreTests/android/core/
DMiscRegressionTest.java467 StackTraceElement trace = traces[traces.length - 2]; in testThreadGetStackTrace() local
471 trace.getClassName().endsWith("$MyThread") && in testThreadGetStackTrace()
472 trace.getMethodName().equals("doSomething")); in testThreadGetStackTrace()
/frameworks/base/core/java/com/android/internal/os/
DRuntimeInit.java139 String trace = SystemProperties.get("ro.kernel.android.tracing"); in commonInit() local
140 if (trace.equals("1")) { in commonInit()
/frameworks/base/test-runner/src/junit/textui/
DResultPrinter.java78 getWriter().print(BaseTestRunner.getFilteredTrace(booBoo.trace())); in printDefectTrace()
/frameworks/base/core/tests/hosttests/src/android/content/pm/
DPackageManagerHostTestUtils.java588 String trace) { in testFailed() argument
590 test.getTestName(), trace)); in testFailed()
/frameworks/base/docs/html/resources/articles/
Dtrack-mem.jd44 can see, in the second table, the stack trace that led to the allocation. Not
/frameworks/base/core/java/android/widget/
DAbsListView.java2008 ViewDebug.trace(scrapView, ViewDebug.RecyclerTraceType.RECYCLE_FROM_SCRAP_HEAP, in obtainView()
2015 ViewDebug.trace(child, ViewDebug.RecyclerTraceType.BIND_VIEW, in obtainView()
2025 ViewDebug.trace(scrapView, ViewDebug.RecyclerTraceType.MOVE_TO_SCRAP_HEAP, in obtainView()
2038 ViewDebug.trace(child, ViewDebug.RecyclerTraceType.NEW_VIEW, in obtainView()
4496 ViewDebug.trace(child,
4520 ViewDebug.trace(child,
5982 ViewDebug.trace(victim, in scrapActiveViews()
/frameworks/base/docs/html/resources/tutorials/testing/
Dactivity_test.jd1018 …The lower pane contains the failure trace. If all the tests are successful, this pane is empty. If…
1019 …then if you highlight a failed test in the upper pane, the lower view contains a stack trace for t…
1032 …test class has failed, find the method or methods that failed, and then use a failure trace to find
1085 …you see a stack trace of the calls that led to the failure. This trace is similar to the following…
1087 …ng/spinnertest_junit_panel_failtrace_callouts.png" alt="The JUnit failure trace" style="height:230…
1091 …The first line of the trace tells you the error. In this case, a JUnit assertion failed. To look a…
1092 …assertion in the test code, double-click the next line (the first line of the trace). In the cente…
/frameworks/base/services/sensorservice/
Dmat.h299 template <typename TYPE, size_t C> static TYPE trace(const mat<TYPE, C, C>& m) { in trace() function
/frameworks/base/docs/html/guide/webapps/
Ddebugging.jd41 <p>Logcat is a tool that dumps a log of system messages. The messages include a stack trace when

12