aMule Forum
English => aMule crashes => Topic started by: Arichy on May 13, 2007, 10:33:46 AM
-
aMule svn-2007-05-02 on Debian GNU/Linux Etch i686
When scrolling through the upload queue (not the list of active uploads), aMule crashes constantliy.
-
I have seen this same issue, however it does not happen frequently, so I've been unable to get a good backtrace of this.
Regards.
-
Could you please try to create a backtrace for this error? (Some help: http://www.amule.org/wiki/index.php/Backtraces)
If there's something about crypto++ in the error message, try recompiling with the embedded crypto++-library.
-
No wuischke, I did not see anything about crypto in the error (however I might be wrong, since I did not save the error, silly me :(). Unfortunately, under solaris the embedded crypto is not an option, since it will compile fine but the resulting aMule is useless (it's unable to create some files on first startup) so I have to use external cryptopp.
Regards.
-
Could you please try to create a backtrace for this error? (Some help: http://www.amule.org/wiki/index.php/Backtraces)
I will try.
I will update
http://www.amule.org/wiki/index.php/Backtraces#Create_a_backtrace
when it's unlocked because for aMule SVN one has to append "--even-if-ifroen-blah-blah" to the aMule command and one cannot do "gdb /usr/local/bin/amule --even-if-ifroen-blah-blah"
It is "gdb /usr/local/bin/amule"
and then "run --even-if-ifroen-blah-blah"
-
Arichy:
You are correct, it is "run --even-if-lfroen-complains-this-will-stay". Thanks for your support.
Skolnick:
Please try running aMule in gdb and with debug support, I see no other way to get a grasp of the problem.
Too bad. Now I have to stop telling people to use the internal crypto++ (solved problems with Ubuntu feisty and possibly Debian) and maybe actually do something for compatibility. (Or a least a list of known incompatibilities.)
Anyway, now that I got a new hard drive for my Athlon Classic I may finally install OpenSolaris and start playing around. (Solaris Express crashed after loading the kernel on the notebook and the Nexenta partitioning manager is very incomprehensible and I couldn't risk loosing data...)
-
[...] try recompiling with the embedded crypto++-library.
I did compile with embedded crypto++-library.
-
Could you please try to create a backtrace for this error?
It's here:
http://forum.amule.org/index.php?topic=12635.0
-
Thanks a lot.
I couldn't find the actual cause, but I'm just a junior code monkey. ;)
Things I believe to know: It's an unknown client (clientImage = 19) with a strange IP value of '0'. I'm not exactly sure whether this is ok, but I see no reason to crash hard either.
I'll try to find out more or you are lucky and one of the more experiences developers knows the cause.
-
OK, thanks to Kry who pointed out an actually pretty obvious error:
0x0826cc71 in CClientCredits::GetCurrentIdentState (this=0x2400, dwForIP=0)
at ClientCredits.cpp:222
A pointer to 0x2400 should never happen. I have no clue what causes this, but I would recommend compiling wxgtk and not using a package.
-
[...] I would recommend compiling wxgtk and not using a package.
I did compile the wxgtk 2.8.3 sources with "./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise". I have no wxgtk or amule packages installed.
-
I can reproduce it here, but it is a memory corruption, as your bactrace has shown, so the backtrace is useless. I'll try to run aMule inside valgrind, but it gets really slow...