Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ChrisMA]

hi Lionel,

I've just installed your package because of the bad performance of the current version. However, the program never starts completely... the windows opens, I can see the listing of the servers, and then it just quits.

Do you have any idea what the problem is? (I'm a Mac newbie...)

Greets from Germany!

[lionel77]

I split your posting from the original thread to keep things better organized, hope you don't mind...

I've tried that version of amule on four different machines with different configurations now and can't reproduce your problem but let's go through two problem shooting strategies:

a) Trying to diagnose the problem
If you start amule via the Termial you get a lot more output about what is going on. Since you said you are relatively new to the Mac I'll try to explain step by step:
- start the application "Terminal" which is located in the "Utilities"-folder inside your "Applications" folder
- you start in your home folder and you want to change to your amule folder using the "cd" command: lets say you put amule in a folder "aMule" in your applications folder then you would enter "cd /Applications/aMule" (and hit return )
- then you need to "cd aMule.app/Contents/MacOS" because this is where the amule executable is
- now you want to start amule with "./amule"
- amule should start now and you should see a lot of output about what amule is doing in the terminal window. if amule stalls again you can post the last two or three output lines here so we have a better idea about where the problem is located

b) Trying to fix it
In rare cases the existing amule configuration files can cause trouble when switching from one version to another. So what we wanna try now is to rename those files so that amule creates new ones upon the next start. (Make sure no version of amule is running before you proceed)
There are two locations for these files:
- inside the "Libray" folder of your home folder is a folder "Preferences", which contains two files: "com.amule.plist" and "eMule Preferences". You now want to rename those using the Finder into something like "com.amule.plist_org" and "eMule Preferences_org".
- the second location is a hidden folder named ".aMule" in your home folder. Since the folder is hidden you can't see it in the Finder, but we can use this as a great opportunity to practice our freshly acquired terminal skills. So switch to terminal again. Just enter "cd" to switch to your home folder. Now use "mv .aMule .aMule_org" to rename this folder so that amule won't use it
- now that we have hidden the old config files from amule we can try to start amule again and see if the problem persists
- in order to restore the old settings (again, while amule is not running) you can just delete the new files in "Preferences" and rename the old ones. To restore the old ".aMule" folder go to the Terminal, use "cd" to make sure you are in your home folder and use "rm -rf .aMule" to delete the new hidden folder. Then use "mv .aMule_org .aMule" to restore the original folder.

Hope this makes sense. Let me now how things work for you.

[ken]

Do we have any reason to believe that the bug in wxMac with unicode enabled has been fixed?  My suspicion is that it hasn't and ChrisMA is encountering a crash because of that.

ChrisMA, to provide useful backtraces, follow these directions similar to the ones lionel77 posted above.

• Open Applications -> Utilities -> Terminal.
• At the command line, type "gdb" and a space, but do not press return yet.
  
• Now, drag the aMule application icon from wherever you keep it and drop it onto the terminal window.  Terminal will type the path to the application onto the command line for you.  It will also add a space after the path.
• Delete the space at the end of the path
• Type "/Contents/MacOS/amule" and press return.  gdb will start up, load some symbols, and then present the prompt "(gdb) ".
• Type "handle SIGPIPE nostop noprint pass" and press return.
• Type "run" and press return.  aMule will start up and run.  As lionel77 suggested, it will write a bunch of information to the terminal window in addition to loading its normal GUI.
• Use aMule as normal until it crashes.  In the GUI, this will be evident when it stops responding completely.  You will get the spinning colorwheel (AKA beachball) cursor.
• Switch back to the terminal.  There should be a message there similar to "Program received signal EXC_BAD_ACCESS, Could not access memory."  and a line of text indicating where in the program the crash happened.  This will be followed by the "(gdb) " prompt.
• Type "bt" and return.  This will print a backtrace.
• Type "bt full" and return.  This will print a backtrace with even more information.
• Copy everything from the "Program received signal..." line to the end of the second backtrace and paste it into a posting here.  You might want to surround the pasted text with [ code ] and [ /code ] tags to make it easier to read (except when you type the tags, don't put in the spaces between the brackets).

Edited to say: The use of the "gdb" debugger throughout the above requires that the Developer Tools are installed.  The Developer Tools are included with your Mac OS X install CDs, but are not installed unless you explicitly choose to install them.  Also, the Tools that came with your install CDs are probably outdated.

To download the up-to-date tools, go to Apple's developer site.  Log in (create a new account if necessary).  Go to "Download Software" -> "Developer Tools" -> "Xcode Tools v1.5" -> "Download".  Then install the downloaded package.

[Kry]

And we will be very thankful if you do it and everyone will be happy and people will praise you

[ChrisMA]

Hi guys,

thank you for all your help. I'm a little bit too busy with studying for some tests right now to check all the suggestions.

It's great that Mac users have this kind of community... there's so much helpfulness...

Thanks!

Chris