From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1337 invoked by alias); 3 Aug 2012 23:48:26 -0000 Received: (qmail 1329 invoked by uid 22791); 3 Aug 2012 23:48:25 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-02-ewr.mailhop.org (HELO mho-02-ewr.mailhop.org) (204.13.248.72) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 03 Aug 2012 23:48:11 +0000 Received: from pool-173-76-45-230.bstnma.fios.verizon.net ([173.76.45.230] helo=cgf.cx) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1SxRbG-000Jzz-OI for cygwin@cygwin.com; Fri, 03 Aug 2012 23:48:10 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id CA3AA429680 for ; Fri, 3 Aug 2012 19:48:09 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+ci0RYFKI3hkXYgZ1WgnVr Date: Sat, 04 Aug 2012 02:14:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: crash on latest cygwin snapshot Message-ID: <20120803234809.GA18316@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20120801125834.GH17949@calimero.vinschen.de> <501A946A.2030102@cornell.edu> <87zk6dcgfg.fsf@Rainer.invalid> <20120802182129.GA11728@ednor.casa.cgf.cx> <87r4rpcdhx.fsf@Rainer.invalid> <20120802193416.GB11728@ednor.casa.cgf.cx> <501B3FE6.90006@cornell.edu> <20120803034119.GA15831@ednor.casa.cgf.cx> <20120803162146.GA15383@ednor.casa.cgf.cx> <501C2E54.6080603@cornell.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <501C2E54.6080603@cornell.edu> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00106.txt.bz2 On Fri, Aug 03, 2012 at 04:02:28PM -0400, Ken Brown wrote: >On 8/3/2012 12:21 PM, Christopher Faylor wrote: >> On Thu, Aug 02, 2012 at 11:41:19PM -0400, Christopher Faylor wrote: >>> On Thu, Aug 02, 2012 at 11:05:10PM -0400, Ken Brown wrote: >>>> On 8/2/2012 3:34 PM, Christopher Faylor wrote: >>>>> On Thu, Aug 02, 2012 at 09:14:50PM +0200, Achim Gratz wrote: >>>>>> Christopher Faylor writes: >>>>>>> Just to be clear: Is this with the recent snapshot? >>>>>> >>>>>> Yes, this is with the 2012-08-01 snapshot. >>>>>> >>>>>>> I ask because one other "I see something similar" seemed to come from >>>>>>> 1.7.16. >>>>>> >>>>>> I'm almost always running a snapshot, but I can back it out to vanilla >>>>>> Cygwin or any other snapshot if it helps finding the error. I don't >>>>>> think I've had any other updates except mesa inbetween switching from >>>>>> the snapshot I used before and the current one ??? but that is >>>>>> circumstancial evidence only. >>>>> >>>>> It would be interesting to see if you or Ken have a problem with the >>>>> 20120730 snapshot. >>>>> >>>>> And, if so, then an strace would probably be useful, although it would >>>>> be huge. If you do get one, let me know how to download it or I can >>>>> provide temporary storage somewhere. >>>> >>>> I do have the same problem with the 20120730 snapshot. I started emacs >>>> in an xterm window, attached strace, and walked away. This time it >>>> didn't take long for emacs to crash, so the strace output isn't huge: >>>> >>>> wget http://sanibeltranquility.com/cygwin/strace.out >>> >>> Thanks. I think I see the problem but I won't be able to get to it >>> tonight. >>> >>> It's in the new signal handling code. >> >> I was actually able to duplicate this fairly easy. It took me too long >> to realize that I had to run the X version of emacs, when that should >> have been obvious from the strace. >> >> I have uploaded a new snapshot which should fix the problem. >> >> Can you confirm Ken? > >I'm testing. It looks good so far, but I'd like to get emacs running >without a crash for 24 hours before I'm confident. I'll report back >tomorrow. > >I'm also testing to see if the recent changes have fixed the problem >that I was struggling with in >http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html . That also >looks good so far. Well, fingers crossed, but I'm not aware of anything which would fix what you describe there. cgf -- 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