aMule Forum

English => Multiplatform => Mac OSX => Topic started by: samson on October 04, 2005, 02:08:22 PM

Title: amuled problems
Post by: samson on October 04, 2005, 02:08:22 PM

i've download aMule-CVS-20051003 and run configure with:

Code: [Select]

./configure --disable-systray --disable-gtk --with-wx-config=../wxMac-2.6.2/build/wx-config --disable-debug --enable-optimize --enable-amule-daemon --enable-amuleweb --enable-amulecmd --disable-monolothic --enable-kad-compile --enable-webserverafter "make" and "sudo make install" i tried to run amuled:

Code: [Select]

samson:~/Desktop/amule-cvs samson$ amuled
16:18:44: Error: Could not unlock mutex (error 2: No such file or directory)
16:18:44: Error: Could not unlock mutex (error 2: No such file or directory)
16:18:44: Error: Could not unlock mutex (error 2: No such file or directory)
16:18:44: Error: Could not unlock mutex (error 2: No such file or directory)
16:18:44: Error: Could not unlock mutex (error 2: No such file or directory)

...the same lines many times...

16:18:46: Error: Could not unlock mutex (error 2: No such file or directory)
16:18:46: Error: Could not unlock mutex (error 2: No such file or directory)
16:18:46: Error: Could not unlock mutex (error 2: No such file or directory)
Segmentation fault
samson:~/Desktop/amule-cvs samson$how can i fix it?

Title: Re: amuled problems
Post by: lfroen on October 04, 2005, 04:37:08 PM

Quote

16:18:44: Error: Could not unlock mutex (error 2: No such file or directory)

Never saw it before, but looks like wx error. Did you compiled it (wx) yourself ?

Quote

Segmentation fault

It would be very helpful to see a backtrace here. Compile with --enable-debug and load resulting core dump into gdb. Then post here or in "Backtraces" forum result of "bt full" command.

Quote

--enable-optimize

- This is not recommended option (not tested).

Title: Re: amuled problems
Post by: ken on October 05, 2005, 05:41:51 AM

By default, Mac OS X has core dumping disabled.  You can enable it, but it is easier to run amuled in gdb in the first place.

I have seen the "Could not unlock mutex" message here, but it only appears once and then amuled works.

Have you ever run aMule with this user account before?  I'm wondering if you have a pre-existing ~/.aMule directory.  There have been recent changes to aMule's source so that it now uses ~/Library/Application Support/aMule as its configuration directory instead.  But the code to relocate a pre-existing ~/.aMule directory to the new location has not received thorough testing, and it may be a problem with that.