Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 27 and Version 28 of TipsForBugReports


Ignore:
Timestamp:
Aug 14, 2010, 2:19:38 AM (13 years ago)
Author:
QuLogic
Comment:

I don't really see why obtaining a debug log is under the topic about crashing

Legend:

Unmodified
Added
Removed
Modified
  • TipsForBugReports

    v27 v28  
    4444The Microsoft Windows `"Error Report"` isn't useful in any way; please '''''do not''''' include it in the bug report.
    4545
    46 === Obtaining a Debug Log ===
     46
     47== All other (non-Windows) OS users ==
     48[wiki:GetABacktrace Get a backtrace]
     49
     50= Debug Logging =
     51== Obtaining a Debug Log ==
    4752If asked to obtain a debug log, the following steps will help you do so.
    4853
     
    5762This will cause the debug output to be saved in a file called `debug.log` in your %USERPROFILE% directory.
    5863
    59 === Preemptive Debug Logging ===
     64== Preemptive Debug Logging ==
    6065Pidgin 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.
    6166
     
    113118
    114119Create a shortcut to the `pidgin.vbs` file on your Desktop (or wherever is convenient) and use that to launch Pidgin.  You can assign the icon from pidgin.exe to the shortcut to make it look nice.
    115 
    116 
    117 == All other (non-Windows) OS users ==
    118 [wiki:GetABacktrace Get a backtrace]
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!