git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] - git-read-tree segfaults
Date: Tue, 10 Mar 2009 20:34:28 +0100	[thread overview]
Message-ID: <35476bd20903101234q71bc520fh18828d7170a4a2f5@mail.gmail.com> (raw)

Hi,

I was following the git core tutorial and git-read-tree got me segfault.
I accidentaly executed the git-read-tree without "-m -u" options and
got segfault.

I can reproduce with the latest git using following script.

-----------------------------------------------
#!/bin/sh

GIT=$1

rm -rf crash; mkdir -p crash; cd crash
$GIT init
echo "xxx" > xxx
$GIT add xxx
$GIT commit -m "xxx"
$GIT checkout -b yyy
echo "yyy" > yyy
$GIT add yyy
$GIT commit -m "yyy"
echo "yyy1" >> yyy
$GIT commit -a -m "yyy1"
$GIT checkout master
echo "xxx1" >> xxx
$GIT commit -a -m "xxx1"
mb=$($GIT merge-base HEAD yyy)
$GIT read-tree $mb HEAD yyy
-----------------------------------------------

regards,
jirka

             reply	other threads:[~2009-03-10 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 19:34 Jiri Olsa [this message]
2009-03-10 19:50 ` [BUG] - git-read-tree segfaults Johannes Schindelin
2009-03-10 20:21 ` Johannes Schindelin
2009-03-11  7:59   ` Jiri Olsa
2009-03-11 12:04     ` Johannes Schindelin
2009-03-12  5:57       ` Junio C Hamano
2009-03-12  7:01         ` Junio C Hamano
2009-03-12  7:29           ` [PATCH] read-tree A B C: do not create a bogus index and do not segfault Junio C Hamano
2009-03-12 14:46             ` Daniel Barkalow
2009-03-12 16:34               ` Linus Torvalds
2009-03-14  6:41                 ` 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=35476bd20903101234q71bc520fh18828d7170a4a2f5@mail.gmail.com \
    --to=olsajiri@gmail.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).