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 16:54:18 +0300 [thread overview]
Message-ID: <5630D38A.7080301@gmail.com> (raw)
In-Reply-To: <5630CF1B.9000706@sociomantic.com>
On 10/28/2015 04:35 PM, Mathias L. Baumann wrote:
> I was using the latest git version 2.6.2 already.
> I suspect it is due to a .gitconfig. This is what is probably required:
>
> ➜ ~ cat .gitconfig
> [diff]
> submodule = log
Yep, that did the trick.
The segfault is from
sha1_file.c:
/* add the alternate entry */
*alt_odb_tail = ent; /* <===== alt_obd_tail is NULL here */
alt_odb_tail = &(ent->next);
ent->next = NULL;
Will try to take a closer look at it.
--
Victor
next prev parent reply other threads:[~2015-10-28 14:11 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
2015-10-28 13:35 ` Mathias L. Baumann
2015-10-28 13:54 ` Victor Leschuk [this message]
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=5630D38A.7080301@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.