Changes between Version 28 and Version 29 of TipsForBugReports


Ignore:
Timestamp:
08/14/10 00:28:08 (9 years ago)
Author:
QuLogic
Comment:

Add non-Windows debug logging

Legend:

Unmodified
Added
Removed
Modified
  • TipsForBugReports

    v28 v29  
    4848[wiki:GetABacktrace Get a backtrace]
    4949
    50 = Debug Logging =
    51 == Obtaining a Debug Log ==
     50= Obtaining a Debug Log =
    5251If asked to obtain a debug log, the following steps will help you do so.
    5352
    5453If Pidgin isn't crashing, you can use the Debug Window (`Help->Debug Window`) to obtain the debug log output.
    5554
    56 If Pidgin is crashing, you can save the debug output to a file by opening a Command Prompt window and starting Pidgin as follows:[[BR]]
     55If Pidgin is crashing, you can save the debug output to a file with the following instructions.
     56
     57== All OS (except Windows) users ==
     58Open a terminal and start Pidgin as follows:
     59{{{
     60pidgin -d 2>&1 > ~/debug.log
     61}}}
     62
     63== Windows ==
     64Open a Command Prompt window and start Pidgin as follows:[[BR]]
    5765(You should replace `C:\Program Files\Pidgin` with the path to which you installed Pidgin if it is different)
    5866{{{
     
    6270This will cause the debug output to be saved in a file called `debug.log` in your %USERPROFILE% directory.
    6371
    64 == Preemptive Debug Logging ==
     72=== Preemptive Debug Logging ===
    6573Pidgin just hiccuped, you want to file a ticket but you wish you had saved the debug log don't you? Here is a script to have it made for you all the time.
    6674
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!