git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victor Leschuk <vleschuk@gmail.com>
To: "Mathias L. Baumann" <mathias.baumann@sociomantic.com>,
	git@vger.kernel.org
Cc: vleschuk@accesssoftek.com
Subject: Re: Bug: Segfault when doing "git diff"
Date: Wed, 28 Oct 2015 15:24:25 +0300	[thread overview]
Message-ID: <5630BE79.40708@gmail.com> (raw)
In-Reply-To: <5630B876.7080407@sociomantic.com>



On 10/28/2015 02:58 PM, Mathias L. Baumann wrote:
> Hello dear git devs,
>
> I just stumbled upon a segfault when doing just "git diff" in my repo.
>
> I managed to create a minimal repo setup where the bug is reproducable.
>
> The problem seems to be a mix of having an untracked submodule and 
> having set an alternates file for one submodule.
>
> Attached you'll find my setup that will reproduce the problem. Simply 
> run  'git diff' in bugtest1.
>
> In case the attachment is refused, I also uploaded it here:
>
> http://supraverse.net/bugdemo.tar.gz
>
> cheers,
>
>     --Marenz
Hello Marenz,

I have just tried to reproduce segfault with the provided archive:

[del@del-debian bugtest1 (master)]$ git diff
diff --git a/submodules/bugtest2 b/submodules/bugtest2
--- a/submodules/bugtest2
+++ b/submodules/bugtest2
@@ -1 +1 @@
-Subproject commit cd0b9ee2946d2df3626943347332a4d86f93b126
+Subproject commit cd0b9ee2946d2df3626943347332a4d86f93b126-dirty

No segfault occured. I am using

git version 2.6.2.308.g3b8f10c

Could you please specify which version of git you are using and also try 
to reproduce it with latest 2.6.2?

--
Victor

  reply	other threads:[~2015-10-28 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 11:58 Bug: Segfault when doing "git diff" Mathias L. Baumann
2015-10-28 12:24 ` Victor Leschuk [this message]
2015-10-28 13:35   ` Mathias L. Baumann
2015-10-28 13:54     ` Victor Leschuk
2015-10-28 14:07     ` [PATCH] add_submodule_odb: initialize alt_odb list earlier Jeff King
2015-10-28 15:24       ` Junio C Hamano
2015-10-28 17:27         ` Jeff King

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=5630BE79.40708@gmail.com \
    --to=vleschuk@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mathias.baumann@sociomantic.com \
    --cc=vleschuk@accesssoftek.com \
    /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).