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:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=HmYUxzzG2QvEwY8rOOsxk28E9XS9K5gzCFypKKDHMDs
	6Fs/Hdd+bi4LwUIEfS/4UXze0NT/288vchE8rGIch0I02+yfroCRh7A5Z15++oHN
	+6oFxmCq6d+DGyGP94uPvxEFZWXihLj430w5R9XsUtuH8ALgd/6yrJZOJ/6NOv3A
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 5 Apr 2015 20:55:04 +0900
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Cygwin hangs up if several keys are typed during outputting a lot of texts.
Message-Id: <20150405205504.cda3df2cc76f7bca7c3d21fb@nifty.ne.jp>
In-Reply-To: <20150404084354.GX13285@calimero.vinschen.de>
References: <20150302204502.39b3e03ad5084b0b5add5d10@nifty.ne.jp>	<20150302144426.GK3213@calimero.vinschen.de>	<20150304203407.14008531b0fb63ad5c19a33f@nifty.ne.jp>	<20150304121952.GL3213@calimero.vinschen.de>	<20150304181857.GM3213@calimero.vinschen.de>	<20150305202456.9ac4815a9d590145e15f7ae2@nifty.ne.jp>	<20150305125901.GX3213@calimero.vinschen.de>	<20150403130735.d04e41875f7defd0e6c2d8d0@nifty.ne.jp>	<20150403113226.GP13285@calimero.vinschen.de>	<20150404155520.8564347f1d42b3c709718aad@nifty.ne.jp>	<20150404084354.GX13285@calimero.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Corinna,

On Sat, 4 Apr 2015 10:43:54 +0200
Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:

> That should have been fixed by cbb9849fa76f1dbe6c66d91b68d9a10f46f1ba69.
> You have to rebuild Cygwin to make this change have an effect.
> 
> Alternatively you could checkout f992ae6f4da99b6a200cfc146b96e8e921ca1e70
> to ignore the ucontext stuff for now.

Hmm, even after cbb9849fa76f1dbe6c66d91b68d9a10f46f1ba69,
it does not work in my environment.

But ok, f992ae6f4da99b6a200cfc146b96e8e921ca1e70 works.

Using f992ae6f4da99b6a200cfc146b96e8e921ca1e70, the problem
you had pointed out has been regenerated. Same problem can
be regenerated with a simple test case below.

#include <windows.h>

int main()
{
	HANDLE hCons;
	DWORD n;

	hCons = GetStdHandle(STD_OUTPUT_HANDLE);
	WriteFile(hCons, "AAAA\n", 5, &n, NULL);
	WriteFile(hCons, "BBBB\n", 5, &n, NULL);
	WriteFile(hCons, "CCCC\n", 5, &n, NULL);
	CloseHandle(hCons);
	return 0;
}

This is caused obviously by the patch I had proposed.
Post processing, in which \n is converted to \r\n, was in
the read process previously, so it had effect to the test
case above.

However, now the post processing is in the write process,
so it does not have effect against direct WriteFile() to
the pipe.

Unfortunately, I have no idea for the moment....

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

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