On Wed, Feb 04, 2009 at 09:34:36PM +0100, Johannes Schindelin wrote: > Hi, > > On Wed, 4 Feb 2009, Adam Thorsen wrote: > > > > > 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. I thought it was not applied, in the end ? Mike -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
