X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sun, 12 Apr 2009 12:49:15 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: TTY write deadlock Message-ID: <20090412164915.GA336@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20090405000347.GA32495@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090405000347.GA32495@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sat, Apr 04, 2009 at 08:03:48PM -0400, Christopher Faylor wrote: >On Sat, Apr 04, 2009 at 03:11:06PM -0700, Josh Stone wrote: >>I've discovered a deadlock in Cygwin which is pretty easy to >>reproduce.?? This seems to happen on all of the console windows I can >>find, except for running in a normal cmd.exe. All of these are >>affected though: xterm, rxvt, mintty, puttycyg+cthelper, and putty >>localhost -> cygwin sshd. > >I can duplicate this. I'll look into fixing it ASAP. 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. cgf -- 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/