git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git status & seg.fault

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Oct 26, 2010, 08:03 UTC
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:
Show 16 quoted lines
> 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?
Previous: Rado Dr.Next: Rado Dr.
Message 2 of 7 in “Fwd: git status & seg.fault”
  1. Rado Dr.Oct 26, 2010
  2. Ævar Arnfjörð BjarmasonOct 26, 2010
  3. Rado Dr.Oct 26, 2010
  4. Ævar Arnfjörð BjarmasonOct 26, 2010
  5. Rado Dr.Oct 26, 2010
  6. Nguyen Thai Ngoc DuyNov 7, 2010
  7. Rado Dr.Nov 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.