Submitted by Nir on Tue, 09/27/2011 - 21:42
I've received a couple of reports about the client crashing in the last few weeks. It's been months since I've had a crash myself, but I'm also not a super-heavy user either. If your client is crashing, the best thing you can do to help me root out these crash-causing bugs is to generate and post a crash report. This is a very simple process on Mac, but a little more involved on Windows.
- Download and unzip drmingw-0.4.4.zip.
- Open a command line window in administrator mode (in Start->Accessories right click Command Prompt and select Run as administrator), navigate to the folder you've extracted above, and install Dr. MingW as your machine's default just-in-time debugger by typing "drmingw -i" without the quotes. You can later remove it by typing "drmingw -u".
- When the client crashes, you should be offered an option to debug it. Select it and a Dr. MingW window should open and produce a detailed crash report.
On Mac OSX:
- Upon crashing, you should get a SoulseekQt quit unexpectedly dialog. Click the Report... button
- If this doesn't immediately produce the report, click the Show Details button.
On Linux: (requires basic familiarity with the Linux command line)
- On the command line change directory to where the SoulseekQt executable is.
- Start SoulseekQt in gdb (refer to your distribution's documentation if you don't have gdb installed): gdb [SoulseekQt executable name]
- In gdb, start SoulseekQt by typing run
- The client should start. Once it crashes, gdb will return to the prompt. Type bt to generate a stack trace of where the crash occurred. Copy the stack trace and proceed as outlined below to post it.
Once you have the report, start a new forum topic using the 'Add content' option to the left and paste it there. Not all crash reports produce useful information, and not every crash report is going to be enough for me to fix the problem, but in most cases it should at least give me some idea of what might have gone wrong.