Re: segfault during clone via http

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 4, 2009, 20:34 UTC
Message-ID: <alpine.DEB.1.00.0902042132110.10279@pacific.mpi-cbg.de>
In-Reply-To: <loom.20090204T183407-350@post.gmane.org>

Hi,

On Wed, 4 Feb 2009, Adam Thorsen wrote:

Show 13 quoted lines

> 
> Here is the stack trace:
> 
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x00494000
> 0x0015bb04 in multi_runsingle ()
> (gdb) bt
> #0  0x0015bb04 in multi_runsingle ()
> #1  0x0015d5af in curl_multi_perform ()
> #2  0x000b8782 in step_active_slots () at http.c:450
> #3  0x000b881c in run_active_slot (slot=0x50a450) at http.c:474
> #4  0x000bac5c in fetch (walker=0x5008d0, 
> sha1=0x4a791c "?u^?9l?\003?5??#??X\"?XL") at http-walker.c:846

FWIW I think the issue is related to the double cleanup I mentioned to Mike Hommey earlier. At least when I undo the double cleanup, I do not get any segfaults anymore.

Ciao, Dscho