Changes between Version 6 and Version 7 of TipsForBugReports

Timestamp:

May 3, 2007, 3:13:48 PM (17 years ago)

Author:

datallah

Comment:

Add information on how to get debug output on windows

TipsForBugReports

@@ -13 +13 @@
 
 == What to do if Pidgin crashes ==
+First make sure that you are not affected by 'Dll Hell' as described above. Download and install the debug version of Win Pidgin. The next time you run Pidgin and it crashes, the call stack will be dumped to pidgin.RPT in your Pidgin install dir. When submitting a bug report, give a detailed description on how to produce your bug and attach the most recent crash dump from your pidgin.RPT
 
-First make sure that you are not affected by 'Dll Hell' as described above. Download and install the debug version of Win Pidgin. The next time you run Pidgin and it crashes, the call stack will be dumped to pidgin.RPT in your Pidgin install dir. When submitting a bug report, give a detailed description on how to produce your bug and attach the most recent crash dump from your pidgin.RPT 
+== 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 cmd shell and starting Pidgin as follows:[[BR]]
+(You should replace `C:\Program Files\Pidgin` with the path to which you installed Pidgin if it is different)
+{{{
+cd "C:\Program Files\Pidgin"
+pidgin.exe -d > debug.log
+}}}
+This will cause the debug output to be saved in a file called `debug.log`.
 
 = All Other Users =