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

Segfault on merge with 1.6.2.1

From
Michael Johnson <redbeard@mdjohnson.us>
Date
Mar 28, 2009, 16:19 UTC
Message-ID
<op.urifmtkkso3nzr@sulidor.mdjohnson.us>
Greetings.

I'm trying to figure out what's going on with a merge I'm trying to do. As far as I know, it's a fairly standard situation, just merging two branches. But I get a segfault each time. This occurs with 1.5.6.5 and 1.6.2.1. The earlier version is on a Debian Etch box with backports.debian.org. The latter is Debian Sid. I also tried on a Windows box with MSysGit 1.6.2.1-preview20090322.exe.

The 1.6.2.1 version just segfaults, but 1.5.6.5 says:

/usr/bin/git-merge: line 438: 32335 Segmentation fault git-merge-$strategy $common -- "$head_arg" "$@" Merge with strategy recursive failed.

In all cases, .git/index.lock is left behind.

I'm using the default configuration, with only a few basic options in my person .gitconfig.

Unfortunately, I cannot post the archive, but I can tar the archive and share that with individuals, if need be.

The problems started with a weird merge by another developer a while ago that somehow reapplied earlier commits. It looked like he had done some commits that wiped some earlier commits but then a commit or two latter the old commits were added back. When I tried to merge the resulting master into my working branch it segfaulted. I didn't have time (or the immediate need) to look into it then and it's been forgotten until now (when, of course, it needs to be done in the next few days :( ).

I have run git gc and also pruned a couple of minor dangling objects. Running git fsck --full reveals no problems. The largest file is about 6MiB.

I've asked on #git, and drizzd there suggested I try here. At this point I'm completely at a loss.

Any help would be greatly appreciated.

Thanks, Michael

-- 
Michael D Johnson   <redbeard@mdjohnson.us>    
redbeardcreator.deviantart.com

"Marketing research...[has] shown that energy weapons that make sounds sell
  better..." - Kevin Siembieda (Rifts Game Master Guide, pg 111)
Next: Miklos Vajna
Message 1 of 18 in “Segfault on merge with 1.6.2.1”
  1. Michael JohnsonMar 28, 2009
  2. Miklos VajnaMar 29, 2009
  3. Michael JohnsonMar 30, 2009
  4. Johannes SchindelinMar 30, 2009
  5. Miklos VajnaMar 30, 2009
  6. Michael JohnsonMar 31, 2009
  7. Michael JohnsonApr 1, 2009
  8. Miklos VajnaApr 1, 2009
  9. Clemens BuchacherApr 1, 2009
  10. Michael JohnsonApr 2, 2009
  11. Clemens BuchacherApr 5, 2009
  12. 1/3 add tests for merging with submodulesClemens Buchacher, Apr 5, 2009
  13. 2/3 update cache for conflicting submodule entriesClemens Buchacher, Apr 5, 2009
  14. 3/3 simplify output of conflicting mergeClemens Buchacher, Apr 5, 2009
  15. Junio C HamanoApr 5, 2009
  16. Johannes SchindelinApr 5, 2009
  17. Michael JohnsonApr 6, 2009
  18. Clemens BuchacherApr 6, 2009

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.