X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=README.markdown;h=9702ba0739294d14c41c8c7eb1264c3491d1391a;hb=b4c584d31d7795428a8a30e353c3f4bc02c5ae5e;hp=4b18e16e9dd94dda1b14d368af4597d3379b67f8;hpb=8ab0d9edc27530b4bc1c3f4f741ce0adacec3caa;p=apitrace diff --git a/README.markdown b/README.markdown index 4b18e16..9702ba0 100644 --- a/README.markdown +++ b/README.markdown @@ -3,7 +3,7 @@ About **apitrace** **apitrace** consists of a set of tools to: -* trace OpenGL, OpenGL ES, D3D9, D3D8, D3D7, and DDRAW APIs calls to a file; +* trace OpenGL, OpenGL ES, Direct3D, and DirectDraw APIs calls to a file; * retrace OpenGL and OpenGL ES calls from a file; @@ -17,9 +17,9 @@ Obtaining **apitrace** To obtain apitrace either [download the latest binaries](https://github.com/apitrace/apitrace/downloads) for your platform if -available, or follow the [build instructions](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. +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. Basic usage @@ -141,6 +141,67 @@ To trace the application inside gdb, invoke gdb as: gdb --ex 'set exec-wrapper env LD_PRELOAD=/path/to/glxtrace.so' --args /path/to/application +### Android ### + +The following instructions should work at least for Android Ice Scream +Sandwitch: + +For standalone applications the instructions above for Linux should +work. 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. + +- Wrapping the android main VM process: + + In the Android root /init.rc add the LD_PRELOAD setting to zygote's + environment in the 'service zygote' section: + + """ + service zygote ... + setenv LD_PRELOAD /data/egltrace.so + ... + """ + + Note that ICS will overwrite the /init.rc during each boot with the + version in the recovery image. So you'll have to change the file in + your ICS source tree, rebuild and reflash the device. + Rebuilding/reflashing only the recovery image should be sufficient. + + +- Copy egltrace.so to /data + + On the host: + $ adb push /path/to/apitrace/build/wrappers/egltrace.so /data + + +- Adjust file permissions to store the trace file: + + By default egltrace.so will store the trace in + /data/app_process.trace. For this to work for applications running + with a uid other than 0, you have to allow writes to the /data + directory on the device: + + # chmod 0777 /data + + +- Enable tracing for a specific process name: + + To trace for example the Settings application: + # setprop debug.apitrace.procname com.android.settings + + In general this name will match what 'ps' reports. + + +- Start the application: + + If the application was already running, for example due to ICS's way + of pre-starting the apps, you might have to kill the application + first: + + # kill + + Launch the application for example from the application menu. + ### Mac OS X ### Run the application you want to trace as @@ -358,16 +419,20 @@ reference software renderer. This can be achieved with retracediff.py script, which invokes glretrace with different environments, allowing to choose the desired GL driver by -manipulating variables such as `LD_LIBRARY_PATH` or `LIBGL_DRIVERS_DIR`. +manipulating variables such as `LD_LIBRARY_PATH`, `LIBGL_DRIVERS_DIR`, or +`TRACE_LIBGL`. -For example: +For example, on Linux: ./scripts/retracediff.py \ --ref-env LD_LIBRARY_PATH=/path/to/reference/GL/implementation \ - -r ./glretrace \ + --retrace /path/to/glretrace \ --diff-prefix=/path/to/output/diffs \ application.trace +Or on Windows: + + python scripts\retracediff.py --retrace \path\to\glretrace.exe --ref-env TRACE_LIBGL=\path\to\reference\opengl32.dll application.trace Links