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=PU
	3G5i+r36QXuX5thk9tV3cQF6H9rHhRxIU30KNm0J45QaqI3M40Krj4q4whhBqOMr
	SkNdORzMGCRiXU271rXUlNjxRhj79MmaDpWQsJCb0V1mcdkLJ8JB8Yye/SC8lq/P
	XEWMH9yfVWbsdUAk1cbqX1EogSaFAfBH0xG2rC5Ls=
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=G/nQOQQ/
	QMX7/BdUrTXTdlMDpT4=; b=yEYoT07du4yGKqH146k8tahbktla3V9jpLLIZCqy
	x5/LFR9OVh0OE+yO6mERP8oMZ1IVwwoVePS9IZ6Qzi1dSu8YNX9P/kRExEdNrB4/
	QQzikY9Riql+EjF2zJbcilYK+JAYVmOpOkm7hmNVJHq602Z+Luby0bgOrf+4rCIe
	LuM=
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_20,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.112.20.199 with SMTP id p7mr13967176lbe.71.1368491028095; Mon, 13 May 2013 17:23:48 -0700 (PDT)
In-Reply-To: <CAHWeT-Z=oQ+Xan7DuRkC1A_7RLAQ5+3oWXQJKDiyPchzyXruQA@mail.gmail.com>
References: <CAP_kE8UJZYf2ebrpDSKtkTrN2p0yT997+y+Z5tr978LNdbTekw AT mail DOT gmail DOT com>	<CAHWeT-Z=oQ+Xan7DuRkC1A_7RLAQ5+3oWXQJKDiyPchzyXruQA AT mail DOT gmail DOT com>
Date: Mon, 13 May 2013 20:23:48 -0400
Message-ID: <CAKepmah+q7ESj4cUQi-MDaPkk+GBdXo-S+b2eeYCRqkxhG7rKg@mail.gmail.com>
Subject: Re: mintty, xterm and rxvt freezes when displaying a binary stream
From: Jack Adrian Zappa <adrianh DOT bsc AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1

On Mon, May 13, 2013 at 5:45 PM, Andy Koppe <andy DOT koppe AT gmail DOT com> wrote:
>
> 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.
>
> http://cygwin.com/ml/cygwin/2013-04/msg00362.html


Sounds like its related, however, if I only send 369 of the 370 lines,
it is fine and the characters sent to the terminal end up on my
command line.  I.e. I get this on my command line after the cat of 369
lines.

$ 1;2c1;2c1;2c

Which is part of the return string sans the leading "\x5b\x3f" a.k.a.
"\e[".  According to that link, you provided, it sounds like only one
key is necessary to cause this problem.

In any case, how does Linux deal with this issue?



Adrian

On Mon, May 13, 2013 at 5:45 PM, Andy Koppe <andy DOT koppe AT gmail DOT com> wrote:
> 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
>

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