aMule Forum
English => aMule Help => Topic started by: JPB on May 19, 2005, 03:07:18 PM
-
I've just done an upgrade from 2.0.0 to the last version, using the SuSE 9.3 rpm from the official download page. On startup (using command line), I get the following output:
jpb@toaster:~> amule
Initialising aMule
Checking if there is an instance already running...
*** glibc detected *** malloc(): memory corruption: 0x085a11c0 ***
Aborted
I had no problem with 2.0.0 - as I haven't run it much yet, I did not experience the issue with the 100% CPI usage. Having now uninstalled 2.0.1 and gone back to 2.0.0, all seems to be well again:
jpb@toaster:~> amule
Initialising aMule
Checking if there is an instance already running...
Loading temp files from /home/jpb/.aMule/Temp.
Loading PartFile 6 of 6
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:6613
*** TCP socket (TCP) listening on 0.0.0.0:6610
*** Client UDP socket (extended eMule) at 0.0.0.0:6611
Empty dir /home/jpb/.aMule/Incoming/ shared
Thought you guys might be able to tell me where the problem lies...
Cheers,
JPB
-
rpm -qa | grep wx
plz
-
Wow - that was quick! :-)
jpb@toaster:~> rpm -qa | grep wx
wxPython2.6-gtk2-unicode-2.6.0.0-rh9_py2.3
wxGTK-2.6.0-1
wxPython-common-gtk2-ansi-2.6.0.0-rh9_py2.4
jpb@toaster:->
-
maybe try before you run amule:
export MALLOC_CHECK_2
then run 2.0.1
cheers ;)
-
That does not seem to have helped. Here's the output:
jpb@toaster:~> su
Password:
toaster:/home/jpb # cd installs
toaster:/home/jpb/installs # rpm -Uvh aMule*.rpm
Preparing... ########################################### [100%]
1:aMule ########################################### [100%]
toaster:/home/jpb/installs # export MALLOC_CHECK_2
toaster:/home/jpb/installs # exit
exit
jpb@toaster:~> amule
Initialising aMule
Checking if there is an instance already running...
*** glibc detected *** malloc(): memory corruption: 0x085a11c0 ***
Aborted
jpb@toaster:~>
-
of course not as root but as the same user that is running amule ;)
-
of course not as root but as the same user that is running amule
Tried both, actually. Same difference. ;-)
-
mhhm, what if your uninstall the python rpms (which are for redhat 9 and not suse anyway)
-
and try maybe: export MALLOC_CHECK_=0
-
Yeah, I know the wxPython rpms are for RedHat, but they are needed to run tovidgui and it says on their site that it generally does not matter that they are not specifically for SuSE.
In any case, why would this not interfere with 2.0.0, but only with 2.0.1?
Anyhow, I did delete the wxPython rpms to check it out. Now this is what I get:
toaster:/home/jpb # cd installs
toaster:/home/jpb/installs # rpm -Uvh aMule*.rpm
Preparing... ########################################### [100%]
1:aMule ########################################### [100%]
toaster:/home/jpb/installs # exit
exit
jpb@toaster:~> export MALLOC_CHECK_=0
jpb@toaster:~> amule
Initialising aMule
Checking if there is an instance already running...
--------------------------------------------------------------------------------A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/board.php?boardid=67
If possible, please try to generate a real backtrace of this crash:
http://www.amule.org/wiki/index.php/Backtraces
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------Current version is: aMule 2.0.1 using wxGTK1 v2.6.0
Running on: Linux 2.6.11.4-20a-default i686
Segmentation fault
I might have to go to bed - it's after midnight here in Australia. I'll have a peek here tomorrow and we can experiment some more perhaps. Thanks for your suggestions, deltaHF.
Cheers, mate.
JPB
-
then there is some other problem ;)
well.. at least a backtrace is needed.
try to catch me on irc when ur awake
cheers