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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=u+3F5fKBgqe074UW8p+pn4oSQbktwX6KfoDghnrQg1oFg1P4qDj2A q8mdASrTygmsF4grnkNqxoqVOYsSGj60AZnbhMAb9EHLVJv883aBO4LwJmZlbXqm xfELVZ0eShehbHTNmHrnNneM7OLyBnhPlCgkgf2lchyrg+n/FyDMjU= 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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=loKUUudFwE7w4dBEV1QxN0sFWBQ=; b=lKDqNv51wMLCSOK1oamyge35LpOk 7EX4dcixL8fD6jlOxfZmT/0wsuhPKUFEqKaURb1IJv+wHWjxC401381LQqkxKfLc qKMdIRRyTT6jkcPINFxiNcwaOJfLH5XNKBjZriZnAKry6tucx3BwZcj2zwOBYUUr 2woEwSvOk2+fsUk= 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 X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 To: cygwin AT cygwin DOT com From: Patrick Jane Subject: Re: Regression with 1.7.20-1 Date: Thu, 11 Jul 2013 15:09:11 +0000 (UTC) Lines: 39 Message-ID: References: <20130610085849 DOT GC28431 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) 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 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? 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 I wonder why? Complex mismatch between unix and Windows signal handling that cygwin must bridge? -- 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