Backtraces

Well, not hard to guess, this is about backtraces.

Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running CVS which can also be unstable sometimes. This is where the backtraces come in: if aMule crashes, and you get an "OOPS - aMule crashed" and so on, we'd like to know. The backtrace aMule provides is not always very usefull as it contains little information, but, as usual, there's a better way: A *real* backtrace.

First of all, you need the GNU Debugger installed. It's called gdb and you could check for that by typing which gdb in a console window. You should see something like this:

$ which gdb
/usr/bin/gdb

If you dont have GDB installed, you will get a message like this:

$ which gdb
which: no gdb in (/bin:/usr/bin:[sic])

If that is the case, the GNU Debugger is most likely not installed on your system and you should install it before you proceed.

Then, compile aMule with debugging information:

$ ./configure --enable-debug --disable-optimise --prefix=/where/to/install/aMule
$ make
$ make install

If you do not want to overwrite you old copy of aMule, simply do this instead:

$ ./configure --enable-debug --disable-optimise
$ make

aMule can then be run by going into the dir src and typing ./amule

If you are unable or unwilling to recompile, or are running a RPM version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.

Now create in your home directory the file .gdbinit and put these lines into it:

ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass

For those who want to know the meaning of the previous lines:

the first one avoid [http://www.gnu.org/software/gdb/gdb.html gdb] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html gdb] stopping at new thread.

To create a backtrace, do the following:

1. Run gdb /where/to/install/aMule/bin/amule
2. Enter run.
3. Use aMule normally until it crashes.
4. Enter bt
5. Enter bt full
6. Post the output of the last two steps in the backtraces forum with some additional comment about the circumstances the segfault happened and what aMule version you used (or checkout time for CVS).

So, that's it, have fun with aMule

Greetings, Citroklar

(Most of the above shamelessly stolen from pure_ascii's post in backtraces forum, thanks, pure!)

Please read this to learn more about GDB and Valgrind.