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

git-fetch segfault in git 1.5.5.1

From
DJDave Jones <davej@redhat.com>
Date
Apr 28, 2008, 18:41 UTC
Message-ID
<20080428184138.GA30702@redhat.com>

Since master.kernel.org updated to latest, I noticed that I could crash git-fetch by doing this..

export KERNEL=/pub/scm/linux/kernel/git/ git fetch $KERNEL/torvalds/linux-2.6 master:linus

(gdb) bt #0 0x000000349fd6d44b in free () from /lib64/libc.so.6 #1 0x000000000048f4eb in transport_unlock_pack (transport=0x7ce530) at transport.c:811 #2 0x000000349fd31b25 in exit () from /lib64/libc.so.6 #3 0x00000000004043d8 in handle_internal_command (argc=3, argv=0x7fffea4449f0) at git.c:379 #4 0x0000000000404547 in main (argc=3, argv=0x7fffea4449f0) at git.c:443 #5 0x000000349fd1c784 in __libc_start_main () from /lib64/libc.so.6 #6 0x0000000000403ef9 in ?? () #7 0x00007fffea4449d8 in ?? () #8 0x0000000000000000 in ?? ()

I then remembered, my .bashrc has this..
export MALLOC_PERTURB_=$(($RANDOM % 255 + 1))
which is handy for showing up such bugs.
More info on this glibc feature is at http://udrepper.livejournal.com/11429.html
	Dave
-- 
http://www.codemonkey.org.uk
Next: Alex Riesen
Message 1 of 3 in “git-fetch segfault in git 1.5.5.1”
  1. Dave JonesApr 28, 2008
  2. Fix use after free() in builtin-fetchAlex Riesen, Apr 28, 2008
  3. Junio C HamanoApr 29, 2008

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.