From: Tor Arvid Lund <torarvid@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: A little mystery - crash caused by empty commit message.
Date: Mon, 16 Feb 2009 11:18:06 +0100 [thread overview]
Message-ID: <1a6be5fa0902160218r65965c18nd3ee90d040702b9@mail.gmail.com> (raw)
In-Reply-To: <20090210153048.GA17660@coredump.intra.peff.net>
On Tue, Feb 10, 2009 at 4:30 PM, Jeff King <peff@peff.net> wrote:
> On Tue, Feb 10, 2009 at 01:58:43PM +0100, Tor Arvid Lund wrote:
>
>> So - after the "+0100" on the committer line, hd tells me (as
>> expected) that I have 0a 0a before "[HIA]". On the "faulty" commit I,
>> for some reason, have 0a 00 instead. I do not understand why, but I
>> guess strchr will return NULL when "\0[HIA]....." is passed to it, and
>> segfault on the next iteration.
>>
>> So - I am no closer to understanding what got me to this state, but
>> your reply was helpful anyway, thanks :-)
>
> Well, it certainly seems like a bug in one of the history-rewriting
> programs. Can you try rebasing, cherry-picking, etc on the original
> version of the commit to see if you can reproduce the breakage?
Hi, I haven't had much time to test this thoroughly, but my primary
suspect is now git-p4 in conjunction with python v2.6, which I
recently installed. I will try to find some time to investigate
further, and let you all know for sure.
-Tor Arvid-
prev parent reply other threads:[~2009-02-16 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 11:15 A little mystery - crash caused by empty commit message Tor Arvid Lund
2009-02-10 11:32 ` Jeff King
2009-02-10 11:46 ` Johannes Sixt
2009-02-10 12:58 ` Tor Arvid Lund
2009-02-10 15:30 ` Jeff King
2009-02-16 10:18 ` Tor Arvid Lund [this message]
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=1a6be5fa0902160218r65965c18nd3ee90d040702b9@mail.gmail.com \
--to=torarvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).