xpra icon
Bug tracker and wiki

Changes between Version 34 and Version 35 of Debugging


Ignore:
Timestamp:
02/08/14 05:48:22 (6 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Debugging

    v34 v35  
    2424{{{#!div class="box"
    2525== Via Logging ==
    26 Sometimes the problem is so obvious that you will simply get the error directly from the command line or in the server log file.
    27 [[BR]]
    2826
    29 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}}}.
    30 The amount of data logged can be overwhelming, especially with the pseudo-category {{{all}}}, so make sure you log it or redirect it to a file that you can then grep to find and extract the data you are looking for.
    31 
    32 [[BR]]
    33 
    34 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.
    35 Use: {{{XPRA_CATEGORY_DEBUG=1 xpra ...}}} to enable debug logging for your chosen {{{CATEGORY}}}.
    36 
    37 [[BR]]
    38 It is also possible to enable and disable debug logging at runtime using:
    39 {{{
    40 xpra control :DISPLAY debug enable CATEGORY
    41 }}}
    42 and
    43 {{{
    44 xpra control :DISPLAY debug enable CATEGORY
    45 }}}
    46 And you can get the current list of debug loggers which:
    47 {{{
    48 xpra control :DISPLAY debug status
    49 }}}
    50 
     27[/wiki/Logging Debug Logging] is the most commonly used debugging technique.
    5128}}}
    5229