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

Re: git-log segfault on 00 graft

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
Mar 5, 2008, 05:27 UTC
Message-ID
<20080305052749.GA23511@atjola.homenet>
In-Reply-To
<Pine.LNX.4.64.0803041954320.7660@fbirervta.pbzchgretzou.qr>
On 2008.03.04 19:57:42 +0100, Jan Engelhardt wrote:
Show 11 quoted lines
> Hi,
> 
> 
> I was playing a bit with grafts, and actually did this:
> 
>   echo '839affa3313011da783b5b8074a5c9805ee8503a 
> 0000000000000000000000000000000000000000' >.git/info/grafts
> 
> running `git log --topo-order` causes a segfault. Yes, I probably 
> "should not be doing that", but I think it at least should not
> segfault.

error: Could not read 0000000000000000000000000000000000000000 fatal: revision walk setup failed

That's what I get with a somewhat up-to-date version from master.
Björn
Previous: Johannes Schindelin
Message 5 of 5 in “git-log segfault on 00 graft”
  1. Jan EngelhardtMar 4, 2008
  2. Johannes SchindelinMar 4, 2008
  3. Shawn O. PearceMar 5, 2008
  4. Johannes SchindelinMar 5, 2008
  5. Björn SteinbrinkMar 5, 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.