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

[Bug] Segfault in git status

From
Dane Jensen <careo@fastmail.fm>
Date
Feb 18, 2008, 08:36 UTC
Message-ID
<F8D3F7F0-3A98-4576-BD89-6E5C682B351C@fastmail.fm>
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.

-Dane
Next: Junio C Hamano
Message 1 of 9 in “[Bug] Segfault in git status”
  1. Dane JensenFeb 18, 2008
  2. Junio C HamanoFeb 19, 2008
  3. Dane JensenFeb 19, 2008
  4. Jay SoffianFeb 21, 2008
  5. Pieter de BieFeb 21, 2008
  6. Jeff KingFeb 21, 2008
  7. Jay SoffianFeb 21, 2008
  8. Pieter de BieFeb 21, 2008
  9. Dane JensenFeb 21, 2008

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.