aMule Forum
English => aMule Help => Topic started by: Belegdol on August 20, 2005, 09:11:50 AM
-
Hi. I have noticed that since yesterday amule is experiencing a crash/lockup sequence. I. e. it crashes and then if run again is locking up. I have my incoming and temp dir on my ext3 partition, aome shared files on ntfs and some on fat32 one. Btw, I can't kill the locked up amule with killall amule, so I am unable to start it again. Guess I'll have to compile with eanble-debug, but how to kill the application? Greets.
-
hey
when you have it compiled in debug, run it in gdb, he should kill it for ya if it crashed
-
Right, but I have not done it yet and now it is an ordinary build.
-
Use "killall -9 amule" for a dirty stab in the back?
-
[jsikorski@DOMOWY aMule-2.0.3]$ killall -9 -v amule
Killed amule(4159) with signal 9
[jsikorski@DOMOWY aMule-2.0.3]$ killall -9 -v amule
Killed amule(4159) with signal 9
[jsikorski@DOMOWY aMule-2.0.3]$ killall -9 -v amule
Killed amule(4159) with signal 9
[jsikorski@DOMOWY aMule-2.0.3]$
Guess I'll have to reboot.
-
Hmm, now running debug version through gdb for 40 minutes and no crash. Maybe another optimisation error by gcc 4.0.1?