diff options
| author | José Fonseca <jfonseca@vmware.com> | 2013-02-05 11:44:26 +0000 |
|---|---|---|
| committer | José Fonseca <jfonseca@vmware.com> | 2013-02-05 11:44:26 +0000 |
| commit | d01f837047b58415474fe7e842521c4d0fbef471 (patch) | |
| tree | f81c748296033872faef5a38244b6db5baf22298 /README.markdown | |
| parent | 2b4c51753aeb95015fa3fba58654bf44ea18a370 (diff) | |
Update Android instructions.
Not really based from personal experience, but rather on what others wrote,
namely
https://github.com/kanru/apitrace/commit/5948e72a25b1d2df07299db0d49f91677827478b
Diffstat (limited to 'README.markdown')
| -rw-r--r-- | README.markdown | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/README.markdown b/README.markdown index 685f221c..1e1d8083 100644 --- a/README.markdown +++ b/README.markdown @@ -152,10 +152,9 @@ To trace the application inside gdb, invoke gdb as: ### Android ### The following instructions should work at least for Android Ice Scream -Sandwitch: +Sandwitch. -For standalone applications the instructions above for Linux should -work. To trace applications started from within the Android VM process +To trace applications started from within the Android VM process (`app_process` aka zygote) you'll have to wrap this process and enable tracing dynamically for the application to be traced. @@ -206,6 +205,15 @@ tracing dynamically for the application to be traced. Launch the application for example from the application menu. +To trace standalone applications do: + + adb push /path/to/apitrace/build/wrappers/egltrace.so /data + adb shell + # cd /data/local/tmp + # LD_PRELOAD=/data/egltrace.so test-opengl-gl2_basic + adb pull /data/local/tmp/test-opengl-gl2_basic.trace + eglretrace test-opengl-gl2_basic.trace + ### Mac OS X ### Run the application you want to trace as |