X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_YG 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: U2FsdGVkX1+DQwBYlHCBzlJZ7t8Z+7EW Date: Sat, 7 Jan 2012 16:09:15 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Issue with 20111222 snapshot Message-ID: <20120107210915.GA30343@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20120106171749 DOT GA20863 AT ednor DOT casa DOT cgf DOT cx> <20120107062121 DOT GA28090 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Sat, Jan 07, 2012 at 08:25:40AM -0500, Chris Sutcliffe wrote: >On 7 January 2012 01:21, Christopher Faylor wrote: >> On Fri, Jan 06, 2012 at 01:57:36PM -0500, Chris Sutcliffe wrote: >>>Sigh... ?it seems to be an issue with the CVS HEAD mksh I'm testing, >>>bash behaves as expected. >> >> You sure it isn't a regression though? ?There has been a lot of work >> in the pipe section of code (which seems to always be the case). > >It does actually seem to be a regression. Testing with mksh 40c and >Cygwin 1.7.9 works as expected, testing with mksh 40c and the 20111222 >snapshot breaks. The interesting thing is that bash works fine, so it >seems to be specific to some interaction between mksh and the >snapshot. > >To recreate the issue, using mksh 40c: > >$ touch test.out >$ tail -f test.out | grep something >Ctrl+C > >The Ctrl+C has no affect. The only way I can get out of the tail is >to kill it from a separate terminal window. I've remembered to attach >the cygcheck output this time. > >If it would be helpful, I can start testing with different snapshots >to see if I can narrow down which snapshot introduced the issue. >Since this is 100% reproducible using mksh for me, hopefully you'll be >able to recreate the issue. I can reproduce this using the release version of mksh. It doesn't seem to be related to my pipe changes but I'll try to fix it ASAP. 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