Re: [Bug] Segfault in git status

From: Jay Soffian <jaysoffian@gmail.com>
Date: Feb 21, 2008, 15:34 UTC
Message-ID: <76718490802210734o43e7eb2fid3f4677d5570ac2a@mail.gmail.com>
In-Reply-To: <F8D3F7F0-3A98-4576-BD89-6E5C682B351C@fastmail.fm>

On Mon, Feb 18, 2008 at 3:36 AM, Dane Jensen <careo@fastmail.fm> wrote:

Show 15 quoted lines

> Hi all-
>
>  Somehow I've managed to create a repository that causes git status to
>  segfault. To be honest, I'm not entirely sure how just yet. This comes
>  after a weekend of splitting a repository into two separate
>  repositories, filtering out a directory from one, and then creating
>  grafts in those repositories to skip commits that now change nothing.
>
>  This was in OS X 10.5.2 with git compiled from cf5c51e. Falling back
>  to 1.5.4.2 cleared it up, so with the help of git bisect I've narrowed
>  the bug down to cf55870.
>
>  I'll spend some time this week trying to find the exact point in my
>  filtering that git status went south and report back if I can
>  replicate it in a more-controlled test.

BTW - you should have a crash log in ~/Library/Logs/CrashReporter and that should list the function in which the crash occurred.

j.