From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10750 invoked by alias); 26 Jun 2012 14:10:47 -0000 Received: (qmail 10731 invoked by uid 22791); 26 Jun 2012 14:10:46 -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; Tue, 26 Jun 2012 14:10:29 +0000 Received: from pool-108-49-31-235.bstnma.fios.verizon.net ([108.49.31.235] helo=cgf.cx) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1SjWTM-0006rQ-MJ for cygwin@cygwin.com; Tue, 26 Jun 2012 14:10:28 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 1C52042967D for ; Tue, 26 Jun 2012 10:10:28 -0400 (EDT) X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+e462JCBw1Q79LsrTW6RS3 Date: Tue, 26 Jun 2012 14:10:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: crash on latest cygwin snapshot Message-ID: <20120626141028.GB22099@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4FE786DA.2050208@gmail.com> <4FE9A2A1.3040802@cornell.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FE9A2A1.3040802@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-06/txt/msg00469.txt.bz2 On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote: >On 6/24/2012 5:30 PM, marco atzeri wrote: >> while building latest atlas I hit a bug that is crashing all the running >> cygwin process. >> It crashes on 20120619 snapshot and also latest cvs source. >> No issue on 20120611 snapshot. > >I'm also seeing this crash, but it does not kill all running cygwin >processes. The only processes that die are the mintty processes and the >associated bash processes. For example, it just happened a few minutes >ago, and XWin survived, along with emacs and xterm. > >It happens intermittently, maybe once every 3 days, and I haven't found >a simple sequence of steps for reproducing it. All I can say for sure >is that I always have more than one mintty running, and they all die. > >Marco, are you sure all cygwin processes die when you experience this >problem? Also, since you can reliably reproduce the crash, have you >tried reverting to the previous version of mintty? Note that mintty was >updated just a few days before the 20120619 snapshot was released. He indicated that some processes kept running. But, hmm. I haven't updated mintty lately. I will try that. 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