Segfaults when staging into destroot

Ryan Schmidt ryandesign at macports.org
Sun Sep 30 23:28:26 PDT 2007


On Sep 22, 2007, at 13:59, Dave Murray-Rust wrote:

> I'm having real hassles with port - most packages fail to install,  
> with a segfault, e.g.:
>
> groke:503:dave>port install tiff
> --->  Fetching zlib
> --->  Verifying checksum(s) for zlib
> --->  Extracting zlib
> --->  Applying patches to zlib
> --->  Configuring zlib
> --->  Building zlib with target all
> --->  Staging zlib into destroot
> tclsh(394) malloc: *** error for object 0x312770: double free
> tclsh(394) malloc: *** set a breakpoint in szone_error to debug
> tclsh(394) malloc: *** error for object 0x312770: double free
> tclsh(394) malloc: *** set a breakpoint in szone_error to debug
> tclsh(394) malloc: *** error for object 0x312770: double free
> tclsh(394) malloc: *** set a breakpoint in szone_error to debug
> --->  Installing zlib 1.2.3_1
> tclsh(394) malloc: *** error for object 0x313760: double free
> tclsh(394) malloc: *** set a breakpoint in szone_error to debug
> tclsh(394) malloc: *** error for object 0x313790: double free
> tclsh(394) malloc: *** set a breakpoint in szone_error to debug
> tclsh(394) malloc: *** error for object 0x3137f0: double free
> tclsh(394) malloc: *** set a breakpoint in szone_error to debug
> Segmentation fault

That should not happen (obviously). Never seen this problem before.

> I've tried using a different tclsh, but the same problem persists.  
> I'm not certain whether port is using the new one... I've exported  
> PATH=/usr/local/bin, and which tclsh points to the newly installed  
> ActiveState tclsh, but I don't know if port uses its own internal  
> version or something?
>
> Any suggestions on where to start debugging this?
>
> So far I've tried uninstalling and reinstalling, selfupgrade,  
> moving fink (/sw) out of the way in case it was causing a conflict,  
> but with no luck. I get this problem on almost all packages.  
> Interestingly, it was not there originally - at least, there are  
> some packages which I had installed before I removed and  
> reinstalled port, which now fail to install.

Make sure you have the latest OS and all updates (10.4.10 or 10.3.9).  
Make sure you have the latest Xcode (2.4.1 for 10.4.10; 1.5 for  
10.3.9). Make sure you have the latest MacPorts (1.5.2). Make sure  
you do NOT have anything at all installed in /sw, /usr/local or any  
other place referenced in your PATH. Just have MacPorts, which is  
usually in /opt/local. It works great by itself, but other software  
installed in other locations can cause unpredictable problems.





More information about the macports-users mailing list