git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-http-fetch Segmentation fault

From
LCLuiz Fernando N. Capitulino <lcapitulino@mandriva.com.br>
Date
May 8, 2007, 19:27 UTC
Message-ID
<20070508162735.6c530a70@localhost>
 Hi,
 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:

""" *** glibc detected *** git-http-fetch: corrupted double-linked list: 0x080a5680 *** """

 It's reproducible with Junio's master and maint branches (3082ac and
53a582 respectivelly).
 BTW, At line 406 (the trap command), git-clone script removes the
directory it was fetching. This removes the core dump file too.
We should not remove the directory if there's a core dump in there.
-- 
Luiz Fernando N. Capitulino
Next: Junio C Hamano
Message 1 of 4 in “git-http-fetch Segmentation fault”
  1. Luiz Fernando N. CapitulinoMay 8, 2007
  2. Junio C HamanoMay 8, 2007
  3. Luiz Fernando N. CapitulinoMay 8, 2007
  4. Luiz Fernando N. CapitulinoMay 8, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.