On Thu, 1 Mar 2007, Eygene Ryabinkin wrote:

Okay, first to clarify: since it isn't doing pipelning, only one easy handle
should use one connectdata struct.

>>> Also, are you using the CVS HEAD libcurl version when you experience these
>>> problems?
>>
>> No, it was 7.16.1. Will try HEAD today or tomorrow.
>
> Got the today's snapshot. SEGV again, but in another place. Both
> git-http-push and git-http-fetch are dumping the core in the same place:
> lib/multi.c:1927 trying to dereference multi->connc->connects[i]->data. It
> is the right place that is dereferencing the bad pointer, because
> ElectricFence is here and seems to do its job ;))

Ouch. That seems to imply that the multi->connc->connects[] array has been
freed? That is done by lib/url.c:Curl_rm_connc() and should only by done on
curl_multi_cleanup() when the multi interface is used...

> Need the clear testcase, will try to write one.

It would be really great! If you fail to repeat it like that an alternative
but harder (for us) approach would be if you could tell us an exact git
version and recipe on how to use it against a puplic repo to repeat the
problem.

Oh, and do try to build libcurl with "configure --enable-debug" and make sure
that git calls curl_memdebug("dump") before starting to use libcurl. It could
possibly provide some clues.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html