git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Ioannis.Kappas@rbs.com
Cc: git@vger.kernel.org
Subject: Re: git svn clone segmentation faul issue
Date: Tue, 28 Jun 2016 13:47:06 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1606281334450.12947@virtualbox> (raw)
In-Reply-To: <0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net>

Hi Ioannis,

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

> 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?

> 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

  reply	other threads:[~2016-06-28 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  8:50 git svn clone segmentation faul issue Ioannis.Kappas
2016-06-28 11:47 ` Johannes Schindelin [this message]
2016-06-28 13:32   ` Johannes Schindelin
2016-06-28 16:13     ` Ioannis Kappas
2016-06-28 16:27       ` Johannes Schindelin
2016-06-29  7:13         ` Johannes Schindelin
2016-06-29  9:00           ` Ioannis Kappas
2016-06-29 11:43             ` Johannes Schindelin
2016-07-01 10:09               ` Ioannis Kappas
2016-07-01 13:41                 ` Johannes Schindelin
2016-06-28 19:48 ` Eric Wong
2016-06-29  8:11   ` Ioannis Kappas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1606281334450.12947@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=Ioannis.Kappas@rbs.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).