Backtraces
Contents
Introduction
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.
The GNU Debugger
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 don't have GDB installed, you will get a message like this:
$ which gdb which: no gdb in (/bin:/usr/bin:[etc])
If that is the case, the GNU Debugger is most likely not installed on your system and you should install it before you proceed.
If your OS is Gentoo Linux you have just to type this:
# emerge -av gdb
Compiling aMule
Then, compile aMule with debugging information:
$ ./configure --enable-debug --disable-optimize --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-optimize $ 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.
Create a backtrace
Now create in your home directory the file .gdbinit and put these lines into it (or you can type them in at the (gdb) prompt later):
ha SIGPIPE nostop noprint pass ha SIG32 nostop noprint pass ha SIG33 nostop noprint pass ha SIG34 nostop noprint pass
For those who want to know the meaning of the previous lines: the first one avoid GDB stopping at broken pipes; the second one avoid GDB stopping at new thread.
To create a backtrace, open a console and do the following:
$ gdb /where/to/install/aMule/bin/amule (gdb) run
Now use aMule normally until it crashes. If it crashes do the following:
(gdb) bt (gdb) bt full (gdb) thread apply all bt
Post the output of the last three commands 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).
The core file
If your aMule executable has been compiled with debug information (--enable-debug configure flag), but you were not running it from within GDB, there is still a way to generate a backtrace, if your system was configured to generate core files.
Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ~/.bashrc:
ulimit -c unlimited
Now, when a program crashes, suppose it generate the file core.1234 (this name can be different, but usually will start with 'core') you can enter GDB like that:
$ gdb --core=/path/to/amule /path/to/core/file/core.1234
and then proceed as in the last session and issue 'bt' and 'bt full'.
So, that's it, have fun with aMule
Greetings, Citroklar & Phoenix
(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.
Links
Version
Created by "Unknown User" on 28.04.04 at 23:21
Updated by Vollstrecker on 22.01.08 at 12:06
