DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type:content-transfer-encoding
	:reply-to; q=dns; s=default; b=JpK8U0GyAXSZ9Q/exm8iHAe691x38iVk+
	R3WO0za/HLNn2xBN1VAMeQPnzcJ98w3+RR7hIbvKnHGcsNnfghPK7D6IJkQ66Nw4
	59/N3cjAbfsINXfMi7lapwYK66BqxSNJicDGn1ZGjdrkRBrqh4OPmwdPF1l7LVQ3
	BwMAstTv0I=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: svn segfault when using svn+ssh schema
To: cygwin@cygwin.com
References: <a1702beb-ff73-0005-6568-2f113ed1ab77@dwalin.fsnet.co.uk>
From: David Rothenberger <daveroth@acm.org>
Message-ID: <9a5a8d1d-2b71-522e-59a6-29ad915e2445@acm.org>
Date: Sun, 8 Jan 2017 12:45:31 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <a1702beb-ff73-0005-6568-2f113ed1ab77@dwalin.fsnet.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com

On 1/8/2017 6:12 AM, Sam Edge wrote:
> I've seen a number of 'svn segfault' threads on the mailing list archive
> but none of them seem to cover this specific failure mode. (Apologies if
> one of them does!)
>
> I'm getting segfaults from svn but only when using ssh as the schema.
> The following three commands are all accessing the same server, the name
> of which has been changed to protect the guilty.
>
> --------
> SamEdge@thor ~
> $ ssh cmserver.XXXXXX.com
> ( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries
> commit-revprops depth log-revprops atomic-revprops partial-replay
> inherited-props ephemeral-txnprops file-revs-reverse ) ) )
> SamEdge@thor ~
> $ svn ls svn+ssh://cmserver.XXXXXX.com/edl/
> Segmentation fault (core dumped)
>
> SamEdge@thor ~
> $ svn ls https://cmserver.XXXXXX.com/edl/
> branches/
> tags/
> trunk/
>
> SamEdge@thor ~
> $
> --------
>
> Access using TortoiseSVN using either schema is working fine, as is
> access from Linux svn.
>
> The server is Ubuntu 14.04.5 LTS with package subversion
> 1.8.8-1ubuntu3.2, openssh-server 1:6.6p1-2ubuntu2.8 and openssl
> 1.0.1f-1ubuntu2.21.
>
> The secure shell access is using public key authentication.
>
> I've attached cygcheck & the segfault stackdump.
>
> I'm at a loss. Any ideas?

[Cygwin subversion maintainer here.]

Sorry, I have no further ideas. svn+ssh is working fine for me here 
using both Cygwin and Debian as the server. Debian is running Subversion 
1.8.10.

I personally lack the technical skills to decode the stack trace. Maybe 
someone else can. Alternatively, you could theoretically download the 
subversion debug package and reproduce the error in gdb to get a 
backtrace. Again, my C/gdb skills are rusty, so I can't provide any 
details about how to do that.

-- 
David Rothenberger  ----  daveroth@acm.org

Doubt is not a pleasant condition, but certainty is absurd.
                 -- Voltaire

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple