From: Dave Jones <davej@redhat.com>
To: git@vger.kernel.org
Subject: git-fetch segfault in git 1.5.5.1
Date: Mon, 28 Apr 2008 14:41:38 -0400 [thread overview]
Message-ID: <20080428184138.GA30702@redhat.com> (raw)
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 reply other threads:[~2008-04-28 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 18:41 Dave Jones [this message]
2008-04-28 20:23 ` [PATCH] Fix use after free() in builtin-fetch Alex Riesen
2008-04-29 7:30 ` Junio C Hamano
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=20080428184138.GA30702@redhat.com \
--to=davej@redhat.com \
--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 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).