I follow the instructions for ftrace here : http://www.linuxforu.com/2010/11/kernel-tracing-with-ftrace-part-1/
Everything works perfectly. I have not been able to execute ftrace before, because the interaction and retrieval of data is done using logical paths.
To execute ftrace , after the correct configuration (many steps ...) inside the adb shell:
root@android :
atrace simplifies the configuration process, so we can access the trace information as follows:
root@android :
On the other hand, I found information on executing strace here: http://www.hokstad.com/5-simple-ways-to-troubleshoot-using-strace
All of these examples have been successfully executed in my environment using the adb shell.
The interaction and access to the results of both tools is very different.
Now I can say that the systrace tool for Android is based on atrace , which in turn is based on ftrace .
strace is also supported, but serves other purposes and does not apply to systrace .
Hi,
source share