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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=wO
	Tx718u5UzSMkGK62BEFjdePLXZNLpiC1NZ0vb1dIouiIloKSlca8hcay2Vm1Xm4D
	XF2ZcovMNmh7rIZfz40Q3ZGvboz1CPTgaSfSfEZkg6BlDwRktsXDrN6R2y+8JuaH
	0uf0oUYC19CdfXEr4Nmwjep0KHOgE1sMhNX+TXZw8=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=1EeDDMGB
	IYYjLj7h45PeO/6X4vg=; b=KCH47Vnq7ULlc6+qpdwznWS/k5okCFSYtHmfv99i
	TcOdlSJyJw2jzrmaTBZ2dVywmv1P7dJk8vVR4vYtYXQW1u5aeFNiJQjbIFB3fkda
	5bq4DwMUC5B/0t6O7/OwKPVtmn5qCLX9fR0qItuoN+GDJ1XdrpzVwSFnZbc2BeyA
	RjU=
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=-3.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS,TW_RX autolearn=ham version=3.3.1
MIME-Version: 1.0
X-Received: by 10.180.21.193 with SMTP id x1mr130973wie.31.1368481517926; Mon, 13 May 2013 14:45:17 -0700 (PDT)
In-Reply-To: <CAP_kE8UJZYf2ebrpDSKtkTrN2p0yT997+y+Z5tr978LNdbTekw@mail.gmail.com>
References: <CAP_kE8UJZYf2ebrpDSKtkTrN2p0yT997+y+Z5tr978LNdbTekw AT mail DOT gmail DOT com>
Date: Mon, 13 May 2013 22:45:17 +0100
Message-ID: <CAHWeT-Z=oQ+Xan7DuRkC1A_7RLAQ5+3oWXQJKDiyPchzyXruQA@mail.gmail.com>
Subject: Re: mintty, xterm and rxvt freezes when displaying a binary stream
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

On 13 May 2013 22:35, Adrian H wrote:
> I inadvertently dumped a binary stream to the terminal and it froze
> mintty.  When I tried to kill the process dumping the data, it
> wouldn't die, even when using -9 switch.  When I used Process Explorer
> to kill it, it died and mintty resumed working.
>
> I narrowed the stream down to 370 'lines' by catting the file and
> heading and tailing its output.  For some reason, I wasn't able to
> narrow it down any further.
>
> This issue doesn't occur within cmd running bash (bash is what is
> running through mintty when this occurred).
>
> I've also tested it with xterm and rxvt and they also froze the
> terminal, so it appears to be something to do with the terminal
> interpreter which may be shared across these three terminal
> programmes.
>
> I've tried to attached the compressed narrowed down stream for you
> viewing pleasure, but this mailing list doesn't support it. If anyone
> wants to debug this further, just tell me where to put the binary file
> and you can do your thing.
>
> Not sure what that stream is doing to the terminal to do that to the
> process, but I don't think it should be doing that.
>
> Any idea what's happening?

http://cygwin.com/ml/cygwin/2013-04/msg00362.html

Andy

--
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