xpra icon
Bug tracker and wiki

Changes between Version 28 and Version 29 of Debugging


Ignore:
Timestamp:
12/05/13 15:42:43 (6 years ago)
Author:
Antoine Martin
Comment:

valgrind update

Legend:

Unmodified
Added
Removed
Modified
  • Debugging

    v28 v29  
    152152
    153153=== In C code ===
    154 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:
    155 {{{
    156 XPRA_UNIX_SOCKET_TIMEOUT=30 xpra attach ...
    157 }}}
    158  for Unix domain sockets (defaults to 5 seconds), or:
    159 {{{
    160 XPRA_INET_SOCKET_TIMEOUT=30 xpra attach ...
    161 }}}
    162  for TCP sockets (defaults to 10 seconds)
     154If 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:
     155{{{
     156XPRA_SOCKET_TIMEOUT=30 xpra attach ...
     157}}}
    163158
    164159=== In python code ===