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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=uFu+Fne2R33N5bFUs7+UmjoZc6Ti8ujzBNmqdGd2BztvRXlhYSR/8
	t7xzS90eBMfZTR/SJCHrepc85LaqbqGMtaym36n0VVNtrFTTni9MGQm4UeukaQbg
	bteEAOa2d+uEb/DNmbDzoZLmfEmgoE916VIimbNPd/5cEmA4lCR0xU=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=6WeKGOdbuUSydMK8eyIOo9nyg38=; b=Ht1TniASCMXVgYZkVFITsKIsQ5KH
	QglJT0DsAHXUYzpQYhRnBt6iFHUSKz2LNHxZJNswZhTAUsqu+qO6UddHayOTLzNq
	yaW+zrmhURO7aVgn5vE2hJIsOXhgmPUBlz6ly2zyTpvIg3qCOtPB9tgS7TjM0/26
	EpPSsbn9OiObSlc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SEMBACKSCATTER,TW_RX autolearn=no version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX184cF7iaxO3fMkUJq5C7yku
Date: Tue, 14 May 2013 01:02:59 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: mintty, xterm and rxvt freezes when displaying a binary stream
Message-ID: <20130514050259.GA6353@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAP_kE8UJZYf2ebrpDSKtkTrN2p0yT997+y+Z5tr978LNdbTekw AT mail DOT gmail DOT com> <CAHWeT-Z=oQ+Xan7DuRkC1A_7RLAQ5+3oWXQJKDiyPchzyXruQA AT mail DOT gmail DOT com> <CAKepmah+q7ESj4cUQi-MDaPkk+GBdXo-S+b2eeYCRqkxhG7rKg AT mail DOT gmail DOT com> <CAHWeT-bSaOUxsACWtFmWaRnhobu22DXrVFa6+6+jqwNdZQhvHw AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHWeT-bSaOUxsACWtFmWaRnhobu22DXrVFa6+6+jqwNdZQhvHw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, May 14, 2013 at 05:39:17AM +0100, Andy Koppe wrote:
>On 14 May 2013 01:23, Jack Adrian Zappa wrote:
>>In any case, how does Linux deal with this issue?
>
>I don't know.  A buffer on the terminal's side of the pty?  Automatic
>deadlock detection in the kernel, causing one of the blocking writes to
>fail?

More likely, I suspect that Linux does not try to use Windows pipes
to emulate ptys and so does not suffer from buffer stalls and races.

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