Changes between Version 48 and Version 49 of Debugging

Timestamp:

06/25/17 22:25:12 (3 months ago)

Author:

Antoine Martin

Comment:

--

Debugging

@@ -106 +106 @@
 }}}
 The packet type is the first thing in each packet and it is a simple string which makes it easy to observe traffic.
-With version 0.9 onwards, it is best to set {{{XPRA_USE_ALIASES=0}}} to ensure that the packets will use plain-text headers rather than numeric aliases.
+It is recommended to set the environment variable {{{XPRA_USE_ALIASES=0}}} to ensure that the packets will use plain-text headers rather than numeric aliases.
 }}}
 
@@ -172 +172 @@
 
 === In C code ===
-If the memory leak is one of the Cython parts or in a C library, use regular tools, like [http://blog.devork.be/2008/12/finding-memory-leaks-in-python.html valgrind]. When using valgrind, the connection timeout may be exceeded because the client will be slowed down. Increasing this timeout will be necessary to be able to use the client with Valgrind. With r4861 onwards, you can do this using the {{{XPRA_SOCKET_TIMEOUT}}} env var:
+If the memory leak is one of the Cython parts or in a C library, use regular tools, like [http://blog.devork.be/2008/12/finding-memory-leaks-in-python.html valgrind]. When using valgrind, the connection timeout may be exceeded because the client will be slowed down. Increasing this timeout will be necessary to be able to use the client with Valgrind. You can do this using the {{{XPRA_SOCKET_TIMEOUT}}} environment variable:
 {{{
 XPRA_SOCKET_TIMEOUT=30 xpra attach ...
@@ -178 +178 @@
 
 === In python code ===
-As of version 0.13, it is possible to get the server to print every 10 seconds the objects which seem to be leaking by starting the server with the environment variable {{{XPRA_DETECT_LEAKS}}} set to {{{1}}}.
+To make the server print the objects which seem to be leaking every 10 seconds, start the server with the environment variable {{{XPRA_DETECT_LEAKS}}} set to {{{1}}}.
 
 [[BR]]