X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Forefront-Antispam-Report: CIP:157.56.238.5;KIP:(null);UIP:(null);IPV:NLI;H:BY2PRD0512HT002.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -3 X-BigFish: PS-3(zzbb2dI98dI9371I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzzz32i2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1155h) Message-ID: <5100B483.9040603@coverity.com> Date: Wed, 23 Jan 2013 23:11:47 -0500 From: Tom Honermann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Subject: Re: Intermittent failures with ctrl-c References: <50F6F69F DOT 3040000 AT coverity DOT com> <20130116185908 DOT GA17801 AT ednor DOT casa DOT cgf DOT cx> <50F70B27 DOT 8000904 AT coverity DOT com> <20130116222305 DOT GA24529 AT ednor DOT casa DOT cgf DOT cx> <50F9AC57 DOT 5020309 AT coverity DOT com> <20130119055833 DOT GA23653 AT ednor DOT casa DOT cgf DOT cx> <50FC6AF2 DOT 7070501 AT coverity DOT com> <50FF56F4 DOT 8090007 AT coverity DOT com> <20130123052650 DOT GA8723 AT ednor DOT casa DOT cgf DOT cx> <51002949 DOT 6070806 AT coverity DOT com> <20130123183539 DOT GB31653 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20130123183539.GB31653@ednor.casa.cgf.cx> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-OriginatorOrg: coverity.com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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 01/23/2013 01:35 PM, Christopher Faylor wrote: > On Wed, Jan 23, 2013 at 01:17:45PM -0500, Tom Honermann wrote: >> I see you checked in a change to detect the infinite recursion. I'd >> call that good enough. > > That probably is relatively ok given that you're trying to terminate the > process anyway but it would be nice to know why the stackdump was > happening. Agreed. I'll investigate and report any future cases I encounter. Tom. -- 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