aMule Forum

English => aMule crashes => Topic started by: wimo on May 03, 2006, 11:14:04 PM

Title: Crash in suse 10.0
Post by: wimo on May 03, 2006, 11:14:04 PM

---------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.1 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.13-15.8-default i686

[2] ?? in amule [0x805ea62]
[3] ?? in amule [0x83e5b08]
[4] ?? in [0xffffe420]
[5] ?? in amule [0x82479b2]
[6] ?? in amule [0x8249fab]
[7] ?? in amule [0x8248de2]
[8] ?? in amule [0x8249019]
[9] ?? in amule [0x824d48d]
[10] ?? in amule [0x824f250]
[11] ?? in amule [0x823e4ed]
[12] ?? in amule [0x824d638]
[13] ?? in amule [0x8255e81]
[14] ?? in amule [0x825a556]
[15] ?? in amule [0x825a311]
[16] ?? in amule [0x8250433]
[17] ?? in amule [0x8260b78]
[18] ?? in amule [0x82660b3]
[19] ?? in amule [0x8264b4a]
[20] ?? in amule [0x8077609]
[21] ?? in amule [0x807858e]
[22] ?? in amule [0x80787fb]
[23] ?? in amule [0x8064e0a]
[24] ?? in amule [0x80d204c]
[25] ?? in amule [0x805e3f6]
[26] ?? in amule [0x83b399a]
[27] ?? in amule [0x80d1f05]
[28] __libc_start_main in /lib/tls/libc.so.6[0x40702ea0]
[29] __gxx_personality_v0 in amule[0x805b591]

Title: RE: Crash in suse 10.0
Post by: phoenix on May 04, 2006, 08:28:55 PM

wimo,

This is totally useless. If you are interested in fixing a problem, please try to compile the suse SRPM yourself WITH DEBUG INFORMATION. This crash does not have a single debug information, those question marks have no information for us.

Cheer!

Title: Re: Crash in suse 10.0
Post by: fredred on May 06, 2006, 09:11:57 AM

phoenix,

here (http://forum.amule.org/thread.php?threadid=9924&sid=) I provided you full debug information ( the same Suse 10.0 ), it still doesn't mean it helps to fix the problem ( no replies ;) )

Title: Re: Crash in suse 10.0
Post by: phoenix on May 09, 2006, 03:47:52 AM

fredred,

Sorry, but the backtraces you are providing have no debug information. Take a look here:
http://www.amule.org/wiki/index.php/Backtraces

In other words, do not forget --enable-debug in ./configure of both aMule and wxWidgets.

Debug information provides us with a little more information than these backtraces you gave. The executables must be explicitly compiled with this option, because this makes them unnecessarily bigger (for a program without bugs). But for programs were you want to find a bug, you need that.

Cheers!