Pidgin
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 7 and Version 8 of TipsForBugReports


Ignore:
Timestamp:
May 5, 2007, 10:57:02 PM (17 years ago)
Author:
datallah
Comment:

Remove the dll hell stuff since it hopefully shouldn't happen anymore

Legend:

Unmodified
Added
Removed
Modified

  • TipsForBugReports

    v7 v8  
    55
    66= Windows Users =
    7 == DLL Hell and Win Pidgin ==
    8 A very common but very unpleasant Windows SNAFU (known as DLL Hell) has been experienced by many Win Pidgin users.
    9 
    10 Symptom: Win Pidgin crashes routinely on startup (but not necessarily just on startup).
    11 
    12 Cause: Dlls with the same name as those that Pidgin uses are found in the dll search path and are used instead of those installed by Pidgin, likely causing Pidgin to malfunction. This can happen when application developers install their dlls to Windows system directories. The most commonly used dll to cause dll hell is zlib.dll.
    13 
    147== What to do if Pidgin crashes ==
    15 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
     8Download and install the debug version of Pidgin for Windows. The next time you run Pidgin and it crashes, the call stack will be dumped to a `pidgin.RPT` file 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`.
    169
    1710== Obtaining a Debug Log ==
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!