From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>,
boiko@mandriva.com.br
Subject: Re: git-http-fetch Segmentation fault
Date: Tue, 8 May 2007 17:23:46 -0300 [thread overview]
Message-ID: <20070508172346.7a2dd910@localhost> (raw)
In-Reply-To: <20070508171310.7e21f5ef@localhost>
Em Tue, 8 May 2007 17:13:10 -0300
"Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br> escreveu:
| Em Tue, 08 May 2007 13:04:47 -0700
| Junio C Hamano <junkio@cox.net> escreveu:
|
| | "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br> escreveu:
| |
| | > A friend of mine reported an easy to reproduce segmentation fault
| | > when cloning through http from his repository:
| | >
| | > """
| | > ~/ git clone http://people.mandriva.com/~boiko/mandrivamenu.git
| | > got 299cdadd846913a052df361e973a947622f23198
| | > walk 299cdadd846913a052df361e973a947622f23198
| | > ...
| | > got 0ecd10d9d6ab020c2469a961777854afda705776
| | > /home/lcapitulino/git//bin/git-clone: line 33: 22353 Segmentation fault (core dumped) git-http-fetch $v -a -w "$tname" "$sha1" "$1"
| | > """
| | >
| | > Sometimes it shows up as a corrupted double-linked list, detected by
| | > glibc:
| |
| | Does not seem to reproduce for me on my x86_64 box nor an i386
| | box I happened to have access to. Both run Debian etch.
|
| Forgot to say that you have to try a few times to reproduce.
And, looks like you need http_proxy set too.
Sorry for the bad report. :-|
--
Luiz Fernando N. Capitulino
prev parent reply other threads:[~2007-05-08 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 19:27 git-http-fetch Segmentation fault Luiz Fernando N. Capitulino
2007-05-08 20:04 ` Junio C Hamano
2007-05-08 20:13 ` Luiz Fernando N. Capitulino
2007-05-08 20:23 ` Luiz Fernando N. Capitulino [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=20070508172346.7a2dd910@localhost \
--to=lcapitulino@mandriva.com.br \
--cc=boiko@mandriva.com.br \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).