From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37651 invoked by alias); 22 Feb 2016 12:02:26 -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 37642 invoked by uid 89); 22 Feb 2016 12:02:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=crashed, brand-new, brandnew, coworker X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 22 Feb 2016 12:02:25 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 056A220B9A for ; Mon, 22 Feb 2016 07:02:23 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Mon, 22 Feb 2016 07:02:23 -0500 Received: from [192.168.1.102] (host86-184-210-93.range86-184.btcentralplus.com [86.184.210.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 44A426800F3 for ; Mon, 22 Feb 2016 07:02:22 -0500 (EST) 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> From: Jon Turney Message-ID: <56CAF8C3.6030801@dronecode.org.uk> Date: Mon, 22 Feb 2016 12:02:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56C73BE9.1080305@sbcglobal.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-02/txt/msg00351.txt.bz2 On 19/02/2016 15:59, Greg Chicares wrote: > On 2016-02-13 18:41, David Rothenberger wrote: >> On 2/9/2016 9:39 AM, Greg Chicares wrote: >>> 'svn' segfaulted on a routine command: [...] >> >> I wasn't able to get any useful information out of the stack trace. >> Running addr2line does not show any functions. I'm not sure if this is >> because you don't have the subversion-debuginfo package installed. I >> would suggest you install this in case it makes a difference and the >> failure happens again. > > I've installed 'subversion-debuginfo' and rebooted. After working okay > for a few days, 'svn' is now segfaulting again. A coworker who did a > brand-new Cygwin installation on a new machine yesterday reports 'svn' > failing for her too, also with a stackdump. > > Here's my failing command: > > /lmi/mirror/lmi[1]$svn update > > Updating '.': > > zsh: segmentation fault (core dumped) svn update > > > (The last line means that 'zsh' caught the segfault, not that zsh crashed.) > > Today's stackdump looks much the same to me as last week's: > > Exception: STATUS_ACCESS_VIOLATION at eip=00000000 > eax=200C6268 ebx=200A8E98 ecx=0022C39C edx=00000000 esi=00000000 edi=00000011 > ebp=200C0250 esp=0022C35C program=C:\cygwin-lmi\bin\svn.exe, pid 1164, thread main > cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 > Stack trace: > Frame Function Args > 200C0250 00000000 (00000000, 00000000, 6C1D5580, 200A0F40) > 200A8E98 00000000 (00000002, 200A8E98, 2009EE70, 200AAF78) > 2009F688 00000000 (6C701180, 6C701160, 00000000, 2009FA28) > 2009EE70 2009F6D8 (00000000, 20052794, 200AAFB0, 00000000) > 20052790 200C8268 (2004D788, 200430F4, 00000000, 20052C08) > 200430F0 2009EE70 (2003EF00, 20038D6C, 20054CB0, 00000000) > 20038D68 20052790 (00000000, 00000000, 20038E88, 00000000) > End of stack trace > > ...and I don't see any useful information from 'addr2line': > > $addr2line -e /usr/bin/svn 0x200c0250 0x2009ee70 0x2009f6d8 > > ??:0 > ??:0 > ??:0 This isn't the right command to use, because addr2line (unlike gdb) doesn't follow .gnu_debuglink pointers, so you need to point it directly at the detached debug symbols from the svn-debuginfo package, i.e. 'addr2line -e /usr/lib/debug/usr/bin/svn.exe.dbg 0x200c0250 0x2009ee70 0x2009f6d8' But I'm afraid this probably still doesn't tell you anything useful, because the exception isn't occurring in svn.exe, but somewhere else. In fact, the addresses in the backtrace look like they are in the heap, so it doesn't look like the stackdump unwinder has managed to record much useful information. -- 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