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

Re: Segfault in xdl_merge is back

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 27, 2006, 11:22 UTC
Message-ID
<Pine.LNX.4.63.0612271214120.19693@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20061227041644.GA22449@spearce.org>
Hi,
On Tue, 26 Dec 2006, Shawn Pearce wrote:
> So I've been able to reproduce the segfault that was earlier reported in 
> xdl_merge.  Unfortunately its in the repo that I can't publish.

So here I am again, wanting to help, being unable to. *Sigh*. At least this time it is due to legal reasons, not unknown ones.

As you said in another mail, Junio suggested using git-merge-file on the blobs themselves. This is a little tricky, since git-merge-file does not read blobs; only files. I'd do this:

	- in merge-recursive.c just before line 658 I'd add an
	  fprintf(stderr, "xdl_merge: %s %s %s\n", sha1_to_hex(a->sha1),
		sha1_to_hex(o->sha1), sha1_to_hex(b->sha1));
	- run the merge until it segfaults
	- get the blobs by using the last three SHA1's in the output by
	  $ git-show <sha1>  > a   # or "o" or "b"
	- $ git merge-file -p a o b >/dev/null

This command line ensures that "a" is not edited, and you can repeat the merge as often as needed.

If this still segfaults, I'd like to have the files privately (I will not look at the contents, as they are irrelevant to this particular bug).

Ciao, Dscho

Previous: Shawn PearceNext: Alexandre Julliard
Message 4 of 15 in “Segfault in xdl_merge is back”
  1. Shawn PearceDec 27, 2006
  2. Linus TorvaldsDec 27, 2006
  3. Shawn PearceDec 27, 2006
  4. Johannes SchindelinDec 27, 2006
  5. Alexandre JulliardDec 27, 2006
  6. xdl_merge(): fix a segmentation fault when refining conflictsJohannes Schindelin, Dec 28, 2006
  7. Junio C HamanoDec 28, 2006
  8. Shawn PearceDec 29, 2006
  9. Johannes SchindelinDec 30, 2006
  10. Jakub NarebskiDec 30, 2006
  11. Johannes SchindelinDec 31, 2006
  12. Jakub NarebskiJan 2, 2007
  13. Johannes SchindelinJan 2, 2007
  14. Junio C HamanoJan 2, 2007
  15. Johannes SchindelinJan 2, 2007

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.