Changes between Version 20 and Version 21 of Debugging

Timestamp:

04/15/13 15:27:51 (8 years ago)

Author:

ahuillet

Comment:

--

Debugging

@@ -156 +156 @@
 == OpenGL ==
 
-Whenever you encounter problems with client-side OpenGL rendering, for example with OpenGL error messages, crashes, or visual artifacts, there are some specific steps to take to investigate.
-The most important thing is to build the tool Apitrace (https://github.com/apitrace/apitrace) according to the documentation https://github.com/apitrace/apitrace/blob/master/INSTALL.markdown, and use it on Xpra to get a full trace.
+Whenever you encounter problems with client-side OpenGL rendering, for example with OpenGL error messages, crashes, or visual artifacts, there are some specific steps to take to investigate. The *Apitrace* tool will get a dump of the OpenGL command stream, allowing it to be sent to the developers for replaying and investigation.
+
+=== Installation of Apitrace ===
+
+==== On Linux ====
+
+Download Apitrace (https://github.com/apitrace/apitrace), build it according to the documentation https://github.com/apitrace/apitrace/blob/master/INSTALL.markdown
+
+==== On Windows ====
+
+You can use pre-built binaries found at http://people.freedesktop.org/~jrfonseca/apitrace/ Try to always use the latest version and fallback to an older one if it doesn't work.
+
+=== Trace generation ===
 
 This trace will enable you to replay the actions of the client without having to re-run it; giving you additional error tracing, ability to send the trace to another person, and ability to replay the exact same steps every time.
@@ -171 +182 @@
 
 Apitrace will replay your trace and report in the bottom panel any errors it found, with additional explanation as compared to what the GL driver typically gives.
+
+Be ready to send the .trace file to the developers for further investigation.