X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <23118994.post@talk.nabble.com> Date: Sat, 18 Apr 2009 19:27:07 -0700 (PDT) From: Josh Stone To: cygwin AT cygwin DOT com Subject: Re: TTY write deadlock In-Reply-To: <20090412164915.GA336@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <20090405000347 DOT GA32495 AT ednor DOT casa DOT cgf DOT cx> <20090412164915 DOT GA336 AT ednor DOT casa DOT cgf DOT cx> X-IsSubscribed: yes 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 Christopher Faylor wrote: > > It took me a while to remember that this is a long standing bug. I > think it is possible to fix thanks to the changes in Cygwin 1.7 but it > isn't a trivial fix. I will still poke at this as I have time but > it may require a minor rewrite of the tty layer to get right. > Hi cgf, thanks for the update. Do you have a bugzilla that I can use to track this? Josh -- View this message in context: http://www.nabble.com/TTY-write-deadlock-tp22888321p23118994.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/