From: Pavel Roskin <proski@gnu.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: git@vger.kernel.org
Subject: Re: Segfaults with USE_CURL_MULTI
Date: Mon, 22 May 2006 11:56:34 -0400 [thread overview]
Message-ID: <1148313394.29228.11.camel@dv> (raw)
In-Reply-To: <87fyj4y1lx.fsf@mid.deneb.enyo.de>
On Sat, 2006-05-20 at 20:47 +0200, Florian Weimer wrote:
> Is anybody else seeing segfaults on dumb HTTP pull with
> USE_CURL_MULTI?
_Everybody_ is seeing them! Just look for "segfaults" in the archives:
http://marc.theaimsgroup.com/?l=git&w=2&r=1&s=segfaults&q=b
This patch looks promising, but I'm yet to test it:
http://marc.theaimsgroup.com/?l=git&m=114816558325617&w=2
> For example, this crashes for me:
>
> $ git clone http://git.enyo.de/fw/debian/debfoster.git upstream
>
> GDB shows that this happens inside the call to curl_multi_perform.
Same for me:
http://marc.theaimsgroup.com/?l=git&m=114790994726570&w=2
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-05-22 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 18:47 Segfaults with USE_CURL_MULTI Florian Weimer
2006-05-20 22:46 ` [PATCH] Remove possible segfault in http-fetch Sean
2006-05-20 22:46 ` Sean
2006-05-20 23:00 ` Florian Weimer
2006-05-21 7:49 ` Junio C Hamano
2006-05-31 16:07 ` Nick Hengeveld
2006-05-22 15:56 ` Pavel Roskin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1148313394.29228.11.camel@dv \
--to=proski@gnu.org \
--cc=fw@deneb.enyo.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.