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

Segfault when fetching from current git.git on GitHub

From
Ralf Thielow <ralf.thielow@gmail.com>
Date
Dec 3, 2013, 18:56 UTC
Message-ID
<CAN0XMOKPWm1CzS3289SHpH=N0osFszuvnK6e9BVxwtQe3b2YJg@mail.gmail.com>
Hi,

I've fetched from the current git.git on GitHub minutes ago and got a segfault. I could reproduce it with the Git version of the current "next" branch (1.8.5.392.gf545f4d) with the steps below. The segfault does not appear with version 1.8.5.

Steps to reproduce: git init tmp cd tmp git remote add origin https://github.com/git/git.git git fetch -v

Full stacktrace: http://pastebin.com/zK8epKWj ProcMaps and ProcStatus from Ubuntu's Apport: http://pastebin.com/ZpPk1WSA

Ralf
Next: Jonathan Nieder
Message 1 of 2 in “Segfault when fetching from current git.git on GitHub”
  1. Ralf ThielowDec 3, 2013
  2. Jonathan NiederDec 3, 2013

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.