Changes between Version 27 and Version 28 of Debugging

Timestamp:

12/05/13 07:58:17 (8 years ago)

Author:

Antoine Martin

Comment:

--

Debugging

@@ -152 +152 @@
 
 === 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.
+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 r4857 onwards, you can do this using env vars, either:
+{{{
+XPRA_UNIX_SOCKET_TIMEOUT=30 xpra attach ...
+}}}
+ for Unix domain sockets (defaults to 5 seconds), or:
+{{{
+XPRA_INET_SOCKET_TIMEOUT=30 xpra attach ...
+}}}
+ for TCP sockets (defaults to 10 seconds)
 
 === In python code ===