Re: SEGV in git-merge recursive:

From: Alex Riesen <raa.lkml@gmail.com>
Date: Mar 29, 2007, 08:18 UTC
Message-ID: <81b0412b0703290118q3e602a7bx650ac41241855546@mail.gmail.com>
In-Reply-To: <20070329075010.GA3493@hermes>

On 3/29/07, Tom Prince <tom.prince@ualberta.net> wrote:

> I have been keeping my Maildir in git, a non-trivial merge that causes a
> segfault in git-merge-recursive.

Can you try and get a stack trace? Do, for example, GIT_TRACE=1 git merge ... ... find the call to git-merge-recursive and start that in gdb. Wait until it crash.

$ 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.