From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: svn segfault when using svn+ssh schema
Date: Mon, 09 Jan 2017 02:04:00 -0000 [thread overview]
Message-ID: <333d0191-3b5b-da0d-bb58-b4e8cc840352@cs.umass.edu> (raw)
In-Reply-To: <9a5a8d1d-2b71-522e-59a6-29ad915e2445@acm.org>
On 1/8/2017 3:45 PM, David Rothenberger wrote:
> 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)
Assuming this is repeatable behavior, perhaps getting a trace using
strace would reveal some more useful information.
Regards - Eliot Moss
--
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
next prev parent reply other threads:[~2017-01-09 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 14:12 Sam Edge
2017-01-08 20:45 ` David Rothenberger
2017-01-08 21:16 ` Jon Turney
2017-01-09 2:04 ` Eliot Moss [this message]
2017-01-09 19:08 ` Sam Edge
2017-01-16 20:07 ` Sam Edge
2017-01-16 20:26 ` Jon Turney
2017-01-16 22:22 ` Sam Edge
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=333d0191-3b5b-da0d-bb58-b4e8cc840352@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).