Changes between Version 28 and Version 29 of TipsForBugReports

Timestamp:

Aug 14, 2010, 5:28:08 AM (13 years ago)

Author:

QuLogic

Comment:

Add non-Windows debug logging

TipsForBugReports

@@ -48 +48 @@
 [wiki:GetABacktrace Get a backtrace]
 
-= Debug Logging =
-== Obtaining a Debug Log ==
+= Obtaining a Debug Log =
 If asked to obtain a debug log, the following steps will help you do so.
 
 If Pidgin isn't crashing, you can use the Debug Window (`Help->Debug Window`) to obtain the debug log output.
 
-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]]
+If Pidgin is crashing, you can save the debug output to a file with the following instructions.
+
+== All OS (except Windows) users ==
+Open a terminal and start Pidgin as follows:
+{{{
+pidgin -d 2>&1 > ~/debug.log
+}}}
+
+== Windows ==
+Open a Command Prompt window and start Pidgin as follows:[[BR]]
 (You should replace `C:\Program Files\Pidgin` with the path to which you installed Pidgin if it is different)
 {{{
@@ -62 +70 @@
 This will cause the debug output to be saved in a file called `debug.log` in your %USERPROFILE% directory.
 
-== Preemptive Debug Logging ==
+=== Preemptive Debug Logging ===
 Pidgin 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.