aMule Forum
English => aMule crashes => Topic started by: microft.pt on April 09, 2005, 01:55:54 PM
-
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
aMule version is: CVS using wxGTK2 v2.5.4 (Snapshot: Wed Apr 6 07:01:21 CEST 2005)
Running on: Linux 2.4.29m i686
- ?? in amuled [0x8100bfd]
[1] ?? in amuled
[0x805e3c8]
[2] wxFatalSignalHandler in /usr/local/lib/libwx_base-2.5.so.4[0x40198ea6]
[3] ?? in /lib/libpthread.so.0 [0x4003bc85]
[4] ?? in /lib/libc.so.6 [0x404addb8]
[5] ?? in amuled [0x808793b]
[6] ?? in amuled [0x8085e8d]
[7] ?? in amuled [0x8084bf7]
[8] ?? in amuled [0x805ec46]
[9] ?? in amuled [0x8062bff]
[10] wxEntry(int&, char**) in /usr/local/lib/libwx_base-2.5.so.4[0x4012cfa9]
[11] ?? in amuled [0x806277d]
[12] __libc_start_main in /lib/libc.so.6[0x4049a469]
[13] ?? in amuled [0x80534f1]
--------------------------------------------------------------------------------
-
could you maybe compile amuled with debug and then run it in gdb?
your output does not help us to much, thnx
btw did you disable udp port? and have max-connections lower tehn 1024?
-
I have:
UDPPort=4672
UDPDisable=0
MaxConnections=500
I've been compiling with:
./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon
-
Someone's using a stripped binary (boo! Hiss!). Please recompile with debugging symbols and run through gdb, that's greatly improve the amount of information we'd get from the crash. ;)
-
what other flags do I have to give to the configure script in order to compile with the debugging symbols?
-
None, just don't run configure with --disable-debug and don't strip the binary afterwards.
-
and to avoid problems set
UDPDisable=0
to 1
this will increase stability a lot
-
I don't even know what "strip the binary" means.
I just compile with those flags and then use checkinstall to create the package to install.
-
I'm guessing that checkinstall strips the binary automatically. You can simply run amuled directly from the src/ directory while testing.