Changes between Version 1 and Version 2 of Logging

Timestamp:

02/08/14 05:47:13 (7 years ago)

Author:

Antoine Martin

Comment:

--

Logging

@@ -3 +3 @@
 
 Sometimes the problem is so obvious that you will simply get the error directly from the command line or in the server log file.
-[[BR]]
+}}}
+
+{{{#!div class="box"
+== Basics ==
 
 Otherwise, a good first step is to start xpra from the command line and add "{{{-d CATEGORY}}}" to it. The list of categories can be found with {{{xpra -d help}}}.
@@ -11 +14 @@
 }}}
 
-[[BR]]
+}}}
 
-Each category can also be enabled using environment variable, which can be useful if you cannot modify the command line, or if the logging should happen very early on, or if you aren't calling the code from its normal wrappers.
+{{{#!div class="box"
+== Environment Variables ==
+
+Each logging category can also be enabled using environment variable, which can be useful if you cannot modify the command line, or if the logging should happen very early on, or if you aren't calling the code from its normal wrappers.
 Use: {{{XPRA_CATEGORY_DEBUG=1 xpra ...}}} to enable debug logging for your chosen {{{CATEGORY}}}.
+
+}}}
+
+{{{#!div class="box"
+== Xpra control interface ==
 
 [[BR]]
@@ -31 +42 @@
 
 }}}
+
+{{{#!div class="box"
+== Detailed Logging ==
+
+Some subsystems require special environment variables to enable logging, this is to minimize the cost of logging in performance critical paths.
+
+For example:
+* x11 event handling:
+{{{
+XPRA_X11_DEBUG_EVENTS="*" xpra start :10
+}}}
+or
+{{{
+XPRA_X11_DEBUG_EVENTS="EnterNotify,CreateNotify" xpra start :10
+}}}
+* {{{XShm}}} and {{{image}}} debugging code:
+{{{
+XPRA_XSHM_DEBUG=1 xpra start :10
+}}}
+or
+{{{
+XPRA_XIMAGE_DEBUG=1 xpra start :10
+}}}
+
+
+Please refer to the source code for details and more up to date information.
+}}}