Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've follow the instructions found here, related to <strong>ftrace</strong>,: <a href="http://www.linuxforu.com/2010/11/kernel-tracing-with-ftrace-part-1/" rel="noreferrer">http://www.linuxforu.com/2010/11/kernel-tracing-with-ftrace-part-1/</a></p> <p>Everything works perfect. I wasn't able to execute <strong>ftrace</strong> before because interacting and retrieving data is done via logical paths. </p> <p>To execute <strong>ftrace</strong>, after correctly configuration (many steps...), inside adb shell:</p> <pre><code>root@android:# cat /sys/kernel/debug/tracing/trace &gt; mytracefile.txt </code></pre> <p><strong>atrace</strong> makes configuration process easier, so we can access to trace information the following way:</p> <pre><code>root@android:# atrace -s -w -t 100 &gt; mytracefile.txt </code></pre> <p>On the other hand, I've found information about executing <strong>strace</strong> here: <a href="http://www.hokstad.com/5-simple-ways-to-troubleshoot-using-strace" rel="noreferrer">http://www.hokstad.com/5-simple-ways-to-troubleshoot-using-strace</a></p> <p>All indicated examples were successfully executed in my environment using adb shell.</p> <p><strong>Interaction and access to results of both tools are very different.</strong> </p> <p>Now I can say that <strong>systrace</strong> Android tool is based in <strong>atrace</strong> which in turn is based in <strong>ftrace</strong>.</p> <p><strong>strace</strong> is also supported but serves to another purposes and is not related to <strong>systrace</strong>.</p> <p>Regards,</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload