X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=UNk1S/4bAABx3dcxq9KmH4l6Jy2yBh+ozI2lIepVEICa4uiwW4Dzo
	SIfEEjs8+MYJDE0yqu67suxjLHRgrG1a5CZ0XuJNsICreKtfbCGsbSq+toGlWrlu
	Tpny0obWsxPbqKgLEUuWmfbVLfrv9JfCpG4HKehpfuDpNnRpKGN5lY=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=jaB+bNzm4KSCIRhTJFGrscrmAiw=; b=EZVe1hXvz0SzRj4RfKS5WObQBL5s
	SEP7yguPEgFdBvxqlox/K3xb9VAiIa3VoMKDalbvvTcqp0bs7JLi2GjKVDFzMeWo
	5ui38O3DfnKhkqPbD/uJP5bK3B1KaYK1WWZQ3ah0/cJzLGTSy4hIPIaR5cSRB7Vv
	dPDrBKfwun6N54U=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19Zwt9sMFfZnNIRiJyAppo8
Date:	Thu, 11 Jul 2013 13:20:26 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Regression with 1.7.20-1
Message-ID:	<20130711172026.GB7515@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAAXzdLVScinNz+YE9+yJ+Pt1hPngBscpwY0eRF==gu8wzyeRnA AT mail DOT gmail DOT com> <CAEhDDbBBkwd_5VuU5T72=L3wzDJYoGEorPeucVOrbYuvpZUcJw AT mail DOT gmail DOT com> <CAAXzdLWw5JPZ8ohs5e6kZiGz9xKM4uKjV4zoN7b5Gg-3wkyW6Q AT mail DOT gmail DOT com> <20130610085849 DOT GC28431 AT calimero DOT vinschen DOT de> <loom DOT 20130711T165420-963 AT post DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<loom.20130711T165420-963@post.gmane.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Jul 11, 2013 at 03:09:11PM +0000, Patrick Jane wrote:
>On Jun 10 03:28, Steven Penny wrote:
>> ...To add more information, running the pipe
>> 
>>   ffmpeg -codecs | grep mov
>> 
>> with 1.7.20-1 just hangs forever, even will ignore Ctrl-C
>
>
>Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>> There's no ffmpeg in the Cygwin distro.  Is that a Cygwin or a native
>> tool?  I guess the latter, in which case you may want to try the
>> latest developer snapshot 2013-06-08 from http://cygwin.com/snapshots/
>
>
>I am pretty sure that I am seeing the same bug with 1.7.20-1 that Steven
>reports.
>
>In my case, I have 4 bash scripts that run in parallel processes.  2 of
>those scripts launch Java programs.  The bug that I see is that Ctrl-C fails
>to kill the Java processes, when it used to work.  The Java command, of
>course, is not built into cygwin but is the Windows program (which you can
>call from cygwin).  I am running Win 7 pro 64 bit.
>
>Being nervous about installing snapshots, I followed Steven's workaround and
>just reran setup.exe, selecting for Base --> cygwin the suggested previous
>version, 1.7.18-1, and installed that.  That old version works perfectly:
>Ctrl-C behaves exactly as expected.
>
>Corinna, do you know when the next prd worthy release of cygwin is likely to
>come out?  Or do I need to monitor http://cygwin.com/ml/cygwin-announce/
>every day to find out?

There is no reason to be nervous about installing snapshots if you think
a new release will solve a problem.  A snapshot potentially always
equals a new release.  Snapshots never break things so severely that you
can't recover by just reinstalling cygwin.

And, yes, you should follow cygwin or cygwin-announce for update
announcements.

>I note that Ctrl-C bugs seem to occur semi-regularly with cygwin:
>http://cygwin.com/ml/cygwin/2012-03/msg00654.html
>http://cygwin.com/ml/cygwin/2013-04/msg00001.html
>http://cygwin.com/ml/cygwin/2012-04/msg00365.html

Those are likely all the same issue.

>I wonder why?  Complex mismatch between unix and Windows signal handling
>that cygwin must bridge?

http://cygwin.com/acronyms#WJM

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 -