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:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=BYKZ2L0fmWa7Uuv0p4EyOJnr3R+h148TuD2KG6V4P3x
	xr8Vw+JY6bf/82UfNyNsU7AmnxRBHLcY8b7sGR2mxe70HwzbdYzBm77s7krnPIVK
	+/xvnA0TyRcgf09+xE+y32r7wk/Ij2OqNnqsUupMbwWd7oBSJTg24+HMEzCkBuMI
	=
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:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=sYDk2ZGRY5HE9ZbTEkAr/3BerJs=; b=FR8smBzzAziRB686M
	NCVIS+HK1BWJf61XmBrHvFiKfLGBUkdAGYMdvxzIqgYpqJNfxVEdYtUkjhqnwDGZ
	SmWSbh3SQqRO6oUfWTb+Jv7gC8KjFCs55b6RKfyWxg+74BPHsdMZnsTKPbhRTXW6
	2XDNsCZQyY4ieon6vGmVmWmVCE=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS_DUL,SPF_PASS autolearn=ham version=3.3.2
X-HELO: conuserg004-v.nifty.com
X-Nifty-SrcIP: [121.93.68.199]
Date: Mon, 13 Apr 2015 19:31:00 +0900
From: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin hangs up if several keys are typed during outputting a lot of texts.
Message-Id: <20150413193100.a393612bde79a4ae57b8c7d9@nifty.ne.jp>
In-Reply-To: <20150407091113.GB2819@calimero.vinschen.de>
References: <20150304203407 DOT 14008531b0fb63ad5c19a33f AT nifty DOT ne DOT jp>	<20150304121952 DOT GL3213 AT calimero DOT vinschen DOT de>	<20150304181857 DOT GM3213 AT calimero DOT vinschen DOT de>	<20150305202456 DOT 9ac4815a9d590145e15f7ae2 AT nifty DOT ne DOT jp>	<20150305125901 DOT GX3213 AT calimero DOT vinschen DOT de>	<20150403130735 DOT d04e41875f7defd0e6c2d8d0 AT nifty DOT ne DOT jp>	<20150403113226 DOT GP13285 AT calimero DOT vinschen DOT de>	<20150404155520 DOT 8564347f1d42b3c709718aad AT nifty DOT ne DOT jp>	<20150404084354 DOT GX13285 AT calimero DOT vinschen DOT de>	<20150405205504 DOT cda3df2cc76f7bca7c3d21fb AT nifty DOT ne DOT jp>	<20150407091113 DOT GB2819 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hi Corinna,

I'm sorry for late reply.

On Tue, 7 Apr 2015 11:11:13 +0200
Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:

> I think we should move opost processing back to the master side.  Would
> it be much of a problem to restructure your patch to do that, without
> re-introducing the old problems your patch fixed?

I am considering of this issue for several days.
However, it is still with dificulty.

For my better understanding, may I ask a question?

At where does cygwin set the standard output handle
for native windows programs to fhandler_pty_slave::
output_handle?

Since I found SetStdHandle() calls in dtable.cc,
I tried to disable all of them. However, the output
of icacls still appears in mintty screen.

I wonder where the standard output handle is set.


By the way,

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

this problem has been gone after the following change.

commit 72f7cd89f230342107ec9e22fea38bf75bcb698d
Author: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Date:   Sat Apr 4 23:31:03 2015 +0100

    Compile exceptions.cc with -fno-omit-frame-pointer on x86

    Selectively using -fomit-frame-pointer when -O is used doesn't make sense
    anymore, apparently since gcc 4.6, -O implies -fomit-frame-pointer.

    exceptions.cc must be compiled with -fno-omit-frame-pointer on x86, as it uses
    RtlCaptureContext, which requires a frame pointer.

        * Makefile.in : Remove setting -fomit-frame-pointer for compiling
        various files, it is already the default.  Set
        -fno-omit-frame-pointer for exceptions.cc on x86.

    Signed-off-by: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>


-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT 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