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

Re: Segfault in git merge-tree (1.8.2.2)

From
John Keeping <john@keeping.me.uk>
Date
May 6, 2013, 13:39 UTC
Message-ID
<20130506133937.GB25912@serenity.lan>
In-Reply-To
<CADEJa-5prhhY-fUHgkk91M8HKWRG3enODS_h7Mq0dgo7V9sYsQ@mail.gmail.com>
On Mon, May 06, 2013 at 03:02:10PM +0200, Andreas Jacobsen wrote:
> I'm getting a segfault in git merge-tree using v1.8.2.2 on MacOS
> 10.8.3. I can't share the repo, but I can build patches and check if
> they fix the problem :)
Can you rebuild with debugging information and try the backtrace again?
Something like:
    make CFLAGS='-O0 -g'
Then use the "git" in bin-wrappers/.
Previous: Andreas JacobsenNext: Andreas Jacobsen
Message 2 of 8 in “Segfault in git merge-tree (1.8.2.2)”
  1. Andreas JacobsenMay 6, 2013
  2. John KeepingMay 6, 2013
  3. Andreas JacobsenMay 6, 2013
  4. John KeepingMay 6, 2013
  5. John KeepingMay 6, 2013
  6. merge-tree: handle directory/empty conflict correctlyJohn Keeping, May 6, 2013
  7. Andreas JacobsenMay 7, 2013
  8. Junio C HamanoMay 7, 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.