X-Recipient:	archive-cygwin AT delorie DOT com
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
X-Mail-Handler:	MailHop Outbound by DynDNS
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19uJA+MzlwY6/xtJhca4P9e
Date:	Tue, 26 Jun 2012 11:04:09 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: crash on latest cygwin snapshot
Message-ID:	<20120626150409.GA23384@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4FE786DA DOT 2050208 AT gmail DOT com> <4FE9A2A1 DOT 3040802 AT cornell DOT edu> <20120626141028 DOT GB22099 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version:	1.0
In-Reply-To:	<20120626141028.GB22099@ednor.casa.cgf.cx>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Tue, Jun 26, 2012 at 10:10:28AM -0400, Christopher Faylor wrote:
>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.

This still just hangs my system by creating many /bin/sh and gcc jobs.
What am I supposed to be seeing for output?  If I set the PATH to just
/usr/bin, I see:

User Override Compilers:
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'
   'none' : 'none' '-fno-common'

and then no more output until I have to restart the machine due to
excessive process creation.

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

- Raw text -