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:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=Mi4BcpkxFTku9DIWm/mcgeft9MQQo
	uNgDvb4klKHSGNOj4OmFZW++iArwtavaCDFYittLjMq+nR/MLr58HyrpPZYLyim7
	cPKH0FSOoR16vznIJkgF2NvIDTNjm4GWKL/VtZWEE6fOLhomF1tZS7FbAbh+9KVb
	ZnLHrmDfu3wNWU=
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:date:message-id:subject:from:to
	:content-type; s=default; bh=N9mHoCN2Z4+BkYQe4eR2l5Vp25M=; b=hMG
	ak3/tmm8i/WD8K1RZ4T/QkkzZLdD8nDHysvTmzZR5Fow6Vk39FtnYZtQzzFsm06X
	JqAB33WG5ubzSA46uhAozncmlSUIxP/c1OH0cNXTQePElvR5H+JD1PKtNP0j99RG
	VGyNZz1UZgCdZeUrE2Ir6RyN1fGgM1iNeCzapkU8=
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=2.8 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,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.60.85.42 with SMTP id e10mr8620473oez.111.1368480909873; Mon, 13 May 2013 14:35:09 -0700 (PDT)
Date:	Mon, 13 May 2013 17:35:09 -0400
Message-ID:	<CAP_kE8UJZYf2ebrpDSKtkTrN2p0yT997+y+Z5tr978LNdbTekw@mail.gmail.com>
Subject:	mintty, xterm and rxvt freezes when displaying a binary stream
From:	Adrian H <adrianh DOT bsc AT gmail DOT com>
To:	cygwin AT cygwin DOT com

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?


Adrian

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

- Raw text -