From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11778 invoked by alias); 2 Aug 2012 14:53:57 -0000 Received: (qmail 11769 invoked by uid 22791); 2 Aug 2012 14:53:56 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_NEUTRAL,TW_CG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from orchid.mail.cornell.edu (HELO orchid.mail.cornell.edu) (132.236.56.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 02 Aug 2012 14:53:42 +0000 Received: from authusersmtp.mail.cornell.edu (granite2.mail.cornell.edu [128.253.83.142]) by orchid.mail.cornell.edu (8.14.4/8.14.4) with ESMTP id q72Ergf6012242 for ; Thu, 2 Aug 2012 10:53:42 -0400 (EDT) Received: from [192.168.1.4] (cpe-67-249-194-47.twcny.res.rr.com [67.249.194.47]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id q72Erbqs020030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 2 Aug 2012 10:53:38 -0400 (EDT) Message-ID: <501A946A.2030102@cornell.edu> Date: Thu, 02 Aug 2012 15:57:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: crash on latest cygwin snapshot References: <4FEA1B54.2030905@gmail.com> <20120626203229.GC26174@ednor.casa.cgf.cx> <4FEA20AB.8060503@gmail.com> <20120626205331.GD26174@ednor.casa.cgf.cx> <20120627014651.GA10400@ednor.casa.cgf.cx> <4FF1B37A.4000902@gmail.com> <20120801094311.GE18636@calimero.vinschen.de> <50190645.2050209@gmail.com> <20120801122902.GC17949@calimero.vinschen.de> <50192522.4090507@cornell.edu> <20120801125834.GH17949@calimero.vinschen.de> In-Reply-To: <20120801125834.GH17949@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown@cornell.edu - Thu Aug 2 10:53:41 2012 X-PMX-CORNELL-REASON: CU_White_List_Override X-IsSubscribed: yes 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 X-SW-Source: 2012-08/txt/msg00048.txt.bz2 On 8/1/2012 8:58 AM, Corinna Vinschen wrote: > On Aug 1 08:46, Ken Brown wrote: >> On 8/1/2012 8:29 AM, Corinna Vinschen wrote: >>> On Aug 1 12:34, marco atzeri wrote: >>>> On 8/1/2012 11:43 AM, Corinna Vinschen wrote: >>>>> Hi Marco, Hi Ken, >>>>> >>>>> On Jul 2 16:43, marco atzeri wrote: >>>>>> On 6/27/2012 3:46 AM, Christopher Faylor wrote: >>>>>>> >>>>>>> Sorry, Marco. Nevermind. I duplicated this. No need to upload anything. >>>>>>> I'm still working on it. >>>>>>> >>>>>>> cgf >>>>>>> >>>>>> >>>>>> it seems solved on 20120702 snapshots >>>>> >>>>> can you please test your crashing scenarios with the latest developer >>>>> snapshot from today? After some private discussion, cgf and I have a >>>>> hunch that the underlying problem was the problem I fixed yesterday, and >>>>> cgf's changes to Makefile.in on 2012-07-01 made just enough changes in >>>>> code optimization so that your problem wasn't visible anymore. >>>>> >>>>> I reverted cgf's changes to Makefile.in and generated the today's >>>>> snapshot specificially to test our hypothesis. Please give it a try. >>>>> >>>>> >>>>> Thanks, >>>>> Corinna >>>>> >>>> >>>> $ uname -a >>>> CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.17s(0.262/5/3) 20120801 11:02:01 >>>> i686 Cygwin >>>> >>>> is not crashing. >>> >>> Thanks for the quick feedback! Now let's see what Ken reports... >> >> I never had a reliable way of reproducing the crash (see >> http://cygwin.com/ml/cygwin/2012-06/msg00464.html). It happened >> seemingly at random, and very sporadically. But I have the snapshot >> installed and will exercise it as much as I can. > > Thanks! The good news: I haven't seen a repeat of that old crash so far. Unfortunately, I'm finding that emacs is unstable: The emacs window (running under X) simply disappears after 12-24 hours. This may not have anything to do with the most recent changes. I haven't yet tested any earlier snapshots. Testing this is a very slow process, since I don't know how to produce the problem; I just have to wait and see if emacs will die. I tried to get some information by running emacs under gdb the most recent time I started it, but all I got was this: (gdb) c Continuing. [Inferior 1 (process 8196) exited with code 05400] (gdb) bt No stack Does that exit code mean anything to you? I couldn't find anything by googling. Ken -- 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