Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: Problem report: pipes and suspending do not work well together Date: Thu, 10 Oct 2002 17:29:33 +0300 Message-ID: <26574F0076BFF449ADAE582D9E67780C0B7FF2@esebe006.ntc.nokia.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: To: X-OriginalArrivalTime: 10 Oct 2002 14:29:33.0717 (UTC) FILETIME=[73D76C50:01C27069] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9AK10q18210 Hello and thanks for your attention, I am using the newest Cygwin net release (upgraded today by re-running Cygwin Setup to make sure this is not fixed yet). I noticed this problem while writing a long pipeline ending with "| less" and then trying to suspend the processes. When I do this the Cygwin window hangs until I kill the processes in the pipeline with "kill" or Windows Task Manager. The simplest testcase I've managed to find is: cat README | less # press ^Z immediately, hangs. Scroll to the bottom and works This one always fails, naturally... yes | less I can reproduce the former case with any text file that is at least 16k long, probably the true value is the number of bytes "less" reads from a pipe when it starts, and this bug happens if you suspend a pipeline where a writer is currently writing to a pipe and blocked because reader hasn't read the data yet. Can't suggest any fixes though. If you have any questions, please Cc: to me also because I'm not on the list. BR, -- Juhani Rantanen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/