On Thu, 7 May 2009, Johannes Schindelin wrote:
Hi, I've encountered a particular merge that causes a segfault, and was
able to successfully bisect git to commit 36e3b5e.
As you already found the commit, you could have Cc:ed me already. It is
pure luck that I did not miss your bug report.
Sorry, didn't think to do so.
After some thought, I was able to come up with a simple script that
reproduces this crash. I'm not sure what the policy on this list is for
attachments, so I've put it at this URL:
http://www.genericorp.net/~count/git-merge-crash
It requires bash and the perl /usr/bin/rename command for simplicity's
sake. At the top of the script is a diagram of what it does.
Hopefully this helps you identify what's happening here. Let me know if
I can help further.
Dave
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html