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

Re: Segmentation fault git read-tree

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Mar 14, 2008, 04:30 UTC
Message-ID
<alpine.LFD.1.00.0803132127281.3557@woody.linux-foundation.org>
In-Reply-To
<alpine.LFD.1.00.0803132125280.3557@woody.linux-foundation.org>
On Thu, 13 Mar 2008, Linus Torvalds wrote:
>
> Ok, I can reproduce this, I'm on it like a maggot on a two-week-dead baby 
> donkey.

Ooh, interesting. Compiling with debugging makes the SIGSEGV go away, and replaces it with an endless loop.

The SIGSEGV when non-debugging seems to be due to a corrupt "info->prev" pointer chain, but this was less obvious than I hoped it would be.

Still looking.
		Linus
Previous: Linus TorvaldsNext: Linus Torvalds
Message 3 of 9 in “Segmentation fault git read-tree”
  1. Len BrownMar 14, 2008
  2. Linus TorvaldsMar 14, 2008
  3. Linus TorvaldsMar 14, 2008
  4. Linus TorvaldsMar 14, 2008
  5. Junio C HamanoMar 14, 2008
  6. Junio C HamanoMar 14, 2008
  7. Junio C HamanoMar 14, 2008
  8. Len BrownMar 14, 2008
  9. Linus TorvaldsMar 14, 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.