d3dretrace: Force DWM traces to run on a window.

[apitrace] / README.markdown

diff --git a/README.markdown b/README.markdown
index b1eb08397aa4bf1a64d1db5b2e7cf3dd11248599..1e1d808329770972b0f0e3829c9b626229294634 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -18,7 +18,7 @@ Obtaining **apitrace**
 ======================
 
 To obtain apitrace either [download the latest
-binaries](https://github.com/apitrace/apitrace/downloads) for your platform if
+binaries](http://apitrace.github.com/#download) for your platform if
 available, or follow the instructions in INSTALL.markdown to build it yourself.
 On 64bits Linux and Windows platforms you'll need apitrace binaries that match
 the architecture (32bits or 64bits) of the application being traced.
@@ -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