Re: git svn clone segmentation faul issue

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 28, 2016, 11:47 UTC
Message-ID: <alpine.DEB.2.20.1606281334450.12947@virtualbox>
In-Reply-To: <0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net>

Hi Ioannis,

On Tue, 28 Jun 2016, Ioannis.Kappas@rbs.com wrote:

Show 12 quoted lines

> Git can fail with a "malformed index nnn" error or cause a segmentation
> fault when executing the "git svn clone" command. 
>
> [...]
>
> Fortunately, a patch has already been submitted to subversion with
> (github) revision a074af86c8764404b28ce99d0bedcb668a321408 (at
> https://github.com/apache/subversion/commit/a074af86c8) on the trunk to
> handle this and a couple of other similar cases. But by the looks of it
> has not been picked up yet in the latest subversion 1.9.4 release or the
> 1.9.x branch, perhaps because this patch was identified in sanity checks
> rather than coming out from a perceivable production issue?

This is an excellent analysis and a silver lining on the horizon to resolve those vexing git svn issues we keep having in Git for Windows.

Do you have a test case that is reliably reproducing the issue?

Show 6 quoted lines

> Although this issue is not in the Git source code, I thought reporting
> this error here first since it is Git that stresses the subversion perl
> bindings in such a level to cause the failure. Perhaps the patch can be
> applied first in those git binary releases that include subversion (I
> believe Git for windows is such a case) while in the mean time I submit
> this case for consideration in the subversion bug tracking system.

Yes, absolutely. Thank you for reporting this!

> The Royal Bank of Scotland plc. Registered in Scotland No 90312.

Oh. I am sorry!

> This e-mail message is confidential and for use by the addressee only.

This footer does not make much sense when sending a mail to a public mailing list ;-)

Ciao, Johannes