Difference between revisions of "Backtraces"
| Line 2: | Line 2: | ||
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. | 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 | + | This is where the bactraces 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. |
| − | + | ||
| − | + | ||
| − | |||
| − | $ gdb | + | 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: | Then, compile aMule with debugging information: | ||
| − | ./configure --enable-debug --disable-optimise --prefix=/where/to/install/aMule | + | $ ./configure --enable-debug --disable-optimise --prefix=/where/to/install/aMule |
| − | make | + | $ make |
| − | make install | + | $ 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 cd'ing to 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. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | To create a backtrace, do the following: | ||
| + | <ol> | ||
| + | <li>Run "gdb /where/to/install/aMule/bin/amule". | ||
| + | <li>Enter "ha SIGPIPE nostop noprint pass" after (gdb) prompt (to avoid gdb stopping at broken pipes). | ||
| + | <li>Enter "ha SIG32 nostop noprint pass" (to avoid gdb stopping at new thread). | ||
| + | <li>Enter "run". | ||
| + | <li>Use aMule normally until it crashes. | ||
| + | <li>Enter "bt". | ||
| + | <li>Enter "bt full". | ||
| + | <li>Post the output of the last two steps in the [http://www.amule.org/amule/board.php?boardid=33&sid= backtraces forum] with some additional comment about the circumstances the segfault happened and what aMule version you used (or checkout time for CVS). | ||
| + | </ol> | ||
| − | |||
| − | |||
So, that's it, have fun with aMule | So, that's it, have fun with aMule | ||
Revision as of 15:07, 30 April 2004
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 bactraces 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 cd'ing to 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.
To create a backtrace, do the following:
- Run "gdb /where/to/install/aMule/bin/amule".
- Enter "ha SIGPIPE nostop noprint pass" after (gdb) prompt (to avoid gdb stopping at broken pipes).
- Enter "ha SIG32 nostop noprint pass" (to avoid gdb stopping at new thread).
- Enter "run".
- Use aMule normally until it crashes.
- Enter "bt".
- Enter "bt full".
- 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!)
