Print

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

[phoenix]

gtoso,

As you are compiling the sources yourself to distribute a binary, you could then remove the assertions or modify the code to be in tune with the current svn.

In the file src/webserver/src/WebInterface.cpp, there are two lines like this:

   wxASSERT(fd >= 2 && fd < FD_SETSIZE);

Here they are lines 101 and 123, but I see from your assertion that one of them is line 95, which corresponds to my line 101 in function AddSocket(). There is another one in function RemoveSocket().

Change them to this (the number 2 becomes a zero):

   wxASSERT(fd >= 0 && fd < FD_SETSIZE);

This is how the current svn code is.

Cheers!

[l3v3l]

New "Bugs" in SVN v. 20080909 (i think this applies to 20080904 too):

#1 - The size of the categories in "Search" (name, filesize, sources, ...) gets not saved, it is resetted at new searches.

#2 - The shown categories in "Downloads" are not saved: I unchecked "Parts" and everytime i restart aMule it shows up again.

Edit: #3  - #1 applies to the categorys in "Networks" (servername, ...) too.


Anyway, thanks for developping to the aMule-Team and for your continuously compiling gtoso!

Greets, l3v3l

[gtoso]

gtoso,

As you are compiling the sources yourself to distribute a binary, you could then remove the assertions or modify the code to be in tune with the current svn.

I did so and I'm going to upload the new debug package.

Code: [Select]

--- aMule-2.2.2/src/webserver/src/WebInterface.cpp.bak  2008-06-07 18:30:13.000000000 +0200
+++ aMule-2.2.2/src/webserver/src/WebInterface.cpp      2008-09-11 04:15:23.000000000 +0200
@@ -92,7 +92,7 @@
         return;
     }
 
-    wxASSERT( (fd > 2) && (fd < FD_SETSIZE) );
+    wxASSERT(fd >= 0 && fd < FD_SETSIZE);
     
     if ( m_gsocks[fd] ) {
         return;
@@ -113,7 +113,7 @@
         return;
     }
     
-    wxASSERT( (fd > 2) && (fd < FD_SETSIZE) );
+    wxASSERT(fd >= 0 && fd < FD_SETSIZE);
     
     int i = m_fd_idx[fd];
     if ( i == 0xffff ) {

Now it works fine,
but it still tells "Bad bundle":

Code: [Select]

2008-09-11 15:52:33: Logger.cpp(275): Debug: wxMacExecute Bad bundle: /Applications/aMule-SVN/aMule.app/Contents/MacOS/amuleweb
2008-09-11 15:52:33: Logger.cpp(275): Debug: pid=7465
2008-09-11 15:52:33: Logger.cpp(275): Debug: Successfully added notification to the runloop
2008-09-11 15:52:33: amule.cpp(844): web server in esecuzione su pid 7465

It's ok from amuled, too.
Similar message:

Code: [Select]

2008-09-11 15:56:25: Logger.cpp(275): Debug: wxMacExecute Bad bundle: amuleweb
2008-09-11 15:56:26: amule.cpp(844): web server in esecuzione su pid 7477


[phoenix]

Hum, "Bad bundle"? This is a Mac only error message. Take a look at src/mac/corefoundation/utilsexc_base.cpp, line 112 in wx2.8.7/wx2.8.8:

    // Create a CFBundle from the CFURL created earlier
    CFBundleRef cfbApp = CFBundleCreate(kCFAllocatorDefault, cfurlApp);

    // Check to see if CFBundleCreate returned an error,
    // and if it did this was an invalid bundle or not a bundle
    // at all (maybe a simple directory etc.)
    if(!cfbApp)
    {
        wxLogDebug(wxT("wxMacExecute Bad bundle: %s"), path.c_str());
        CFRelease(cfurlApp);
        return errorCode ;
    }

Unfortunately, I have no knowledge about Mac specific code. From what I can read, the variable "errorCode" does not help, it is a constant created at the start of the routine. You should investigate the reasons why CFBundleCreate() could fail.

Cheers!

[xja]

I had a crash upon start, thank goodness I launched aMule via Terminal, here's the output.
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
HTTP download thread started
ListenSocket: Ok.
HTTP download thread started
Loading temp files from /Users/privato/Library/Application Support/aMule/Temp.
Loading PartFile 5 of 5
All PartFiles Loaded.
Adding file /Users/privato/Library/Application Support/aMule/Temp/006.part.met to shares
Adding file /Users/privato/Library/Application Support/aMule/Temp/009.part.met to shares
HTTP download thread started
Host: amule.sourceforge.net:80
URL: http://amule.sourceforge.net/lastversion
Host: emulepawcio.sourceforge.net:80
URL: http://emulepawcio.sourceforge.net/ipfilter.zip
Response: 0 (Error: 1)
WARNING: Void response on stream creation
Response: 0 (Error: 1)
WARNING: Void response on stream creation
HTTP download thread ended
HTTP download thread ended

--------------------------------------------------------------------------------
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/index.php?board=67.0
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.2.2 using wxMac v2.8.8
Running on: Mac OS X (Darwin 8.11.1 i386)

--== no BACKTRACE for your platform ==--



--------------------------------------------------------------------------------
Abort trap

And this is the (not quite normal) crash report

Host Name:      MacBook-Frt
Date/Time:      2008-09-17 19:10:36.990 +0200
OS Version:     10.4.11 (Build 8S2167)
Report Version: 4

Command: amule
Path:    /Applications/aMule.app/Contents/MacOS/amule
Parent:  bash [255]

Version: 2.2.2 (2.2.2)

PID:    276
Thread: Unknown

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Backtrace not available

Unknown thread crashed with X86 Thread State (32-bit):
  eax: 0x00000000  ebx: 0x00198448  ecx: 0xa0c7da64  edx: 0x00000000
  edi: 0x16fbfd20  esi: 0x16f627c0  ebp: 0xb02b1ed8  esp: 0xb02b1eb0
   ss: 0x0000001f  efl: 0x00010282  eip: 0x001983d2   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037

Binary Images Description:

Bye

[xja]

Hi there,
I finally upgraded to Leopard, it seems that aMule is more stable in Leopard, since I experienced fewer crashes (totally random ones).
It would be nice if aMule sort users in the downloads pane correctly.
When you expand a file entry aMule sometimes arranges users in a seemingly random order, often file entries and users are mixed together, is a mess!
In 2.1 sorting users worked fine.
Another issue is a graphical one, when aMule downloads the server list and other stuff, the rabbit in the status window jumps, then it come back abruptly, also this animation were shown correctly in 2.1.

Bye.

[yoast]

Will there be a new OS X binary for aMule 2.2.3? Preferably by gtoso, since he is 'Official MacOSX Packager' - noblesse oblige

[rigodon]

http://www.macupdate.com/info.php/id/16818/amule

Everything is here :
http://gtoso.tor.it/pub/amule/osx/2.2.3/

[yoast]

Thanx  , totally missed that one 

[rigodon]

2.2.4 ? 

[gtoso]

2.2.4 ? 

Soon

[rigodon]

Thanks ! Any differences for the mac version ?

[mirko.g]

UPDATE: take a look to this thread http://www.amule.org/amule/index.php?topic=16788.0

[Kry]

Soon

I'm glad we made this guy an official contributor. He's totally in our wavelength.

[Ambrose]

Regrettably, the MacFactory  2.2.4 Universal Binary build does not work on Tiger unless the user has previously installed aMule via MacPorts. Doing so installs the correct (version 7.0.0) libiconv.2.dylib library file.

Using the 10.4 SDK in Leopard's Developer Tools to compile for Tiger does not warn that library version 7.0.0. does not exist in Tiger, since it does exist in Leopard. (A web search on "libiconv.2.dylib version" will show the trouble this has caused.) The problem of Tiger's incompatible version 5.0.0 libiconv.2.dylib was first mentioned here in Reply #15 of this thread.

Binary package creators might want to consider that only the more adventurous Mac users are willing to use MacPorts to install applications. The great majority of people are comfortable installing only pre-compiled binaries, so any reference an executable makes to an item in /opt/local/ will fail, as that directory exists only when and if it is created by Mac Ports. gtoso's posts in this thread are most informative in explaining related issues, such as aMule crashing on startup because it expected to find an existing .dat file for GeoIP in the /opt/local/ directory.