Re: A little mystery - crash caused by empty commit message.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 10, 2009 at 4:30 PM, Jeff King <peff@xxxxxxxx> 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-
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux