From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37584 invoked by alias); 20 Feb 2016 02:41:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 37571 invoked by uid 89); 20 Feb 2016 02:41:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Greg, mirror, someday, zsh X-HELO: nm17-vm4.access.bullet.mail.gq1.yahoo.com Received: from nm17-vm4.access.bullet.mail.gq1.yahoo.com (HELO nm17-vm4.access.bullet.mail.gq1.yahoo.com) (216.39.63.105) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sat, 20 Feb 2016 02:41:49 +0000 Received: from [216.39.60.167] by nm17.access.bullet.mail.gq1.yahoo.com with NNFMP; 20 Feb 2016 02:41:47 -0000 Received: from [67.195.23.144] by tm3.access.bullet.mail.gq1.yahoo.com with NNFMP; 20 Feb 2016 02:41:47 -0000 Received: from [127.0.0.1] by smtp116.sbc.mail.gq1.yahoo.com with NNFMP; 20 Feb 2016 02:41:47 -0000 X-Yahoo-SMTP: mjD.OBqswBAPbVUxYJaYPvc61jLEnpq8VnBwJGdbEJOPA9xw Subject: Re: subversion 1.9.3-1 segfault To: cygwin@cygwin.com References: <56BA2465.9040809@sbcglobal.net> <56BF78DF.7090000@acm.org> <56C73BE9.1080305@sbcglobal.net> <56C742BD.3040503@acm.org> From: Greg Chicares Message-ID: <56C7D26A.1090507@sbcglobal.net> Date: Sat, 20 Feb 2016 02:41:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 MIME-Version: 1.0 In-Reply-To: <56C742BD.3040503@acm.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00307.txt.bz2 On 2016-02-19 16:28, David Rothenberger wrote: > Greg Chicares wrote: [...] >> /lmi/mirror/lmi[1]$svn update >> Updating '.': >> zsh: segmentation fault (core dumped) svn update [...non-helpful stackdump...] >> I'll try running 'svn' under 'gdb'. Is there anything else I can do to help? > > That's the only other thing I can think of. If you can catch the > segfault and get a backtrace, I may be able to track it down. Thanks. The problem is no longer occurring. Let me state what I know for the record in case it helps someone else someday. This seems to be a heisenbug. When I ran it under gdb, repeatedly, it refused to segfault. Outside gdb, with subversion-debuginfo installed, I was unable to get a useful stackdump. The problem has occurred only when gnu.org's svn server is slow: on one isolated occasion a week or two ago, and throughout today. And today there seems to have been a DDOS attack on gnu.org: https://savannah.gnu.org/support/?108973 While the problem lasted, sometimes I got one or both of these messages: svn: E170013: Unable to connect to a repository svn: E175012: Connection timed out and sometimes svn segfaulted with no message. I tried the same operations on my debian-7 ("wheezy") system with its older svn-1.6.17, where I got timeouts but no segfault. My real problem was the gnu.org server. I can only conjecture that attempting to work with a server under extreme load causes svn-1.9.3-1 to follow some exceptional code path that attempts to report a diagnostic and in doing so sometimes crashes. -- 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