From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Tue, 26 Oct 2010 08:03:07 GMT
Subject: Re: git status & seg.fault
Message-ID: <AANLkTikhU+hBwsh24JYGmwHoNFGMseAx_+rUMYH4XGkT@mail.gmail.com>
In-Reply-To: <AANLkTinghepgdMRjEBhpAMz-Mr0g7szKyYEDfE=ttstS@mail.gmail.com>

On Tue, Oct 26, 2010 at 08:44, Rado Dr. <radodr@gmail.com> wrote:
> I have "Segmentation fault" error after "git status" command in one of
> my local repos. Just i one repo, other repos are OK. I can't find any
> clue how to fix it, and as usually I need work with that repo ;-)
>
> I tried this:
>  - git gc  -> OK
>  - git fsck ->
> missing blob 0000000000000000000000000000000000000000
> dangling blob 2f1f0144f786ca887c4911a064bbb28a047f1f77
> dangling blob 7ffb0f4e430cd60261661138df61ecb50cf1d0a4
>
> Is this the reason of fault? If yes, how can I fix it.
>
> My system info:
> Linux 32bit, Ubuntu 10.04 LTS - Lucid Lynx,
> git version 1.7.0.4

Can you reproduce it on the latest version of git built from git.git?

Can you run it under gdb and provide a "bt full" backtrace?