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:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=TI8H4LccfCWL6Z7SSEFq/0u9G9iGuvPPDZfF6eMTYU5A055x+wrWS
	7PL9gRZdZKWoQcewL99eJqd68XTzsuJI6b5rFNkopMBlgY3CbbP4DovzvHBrh3Pe
	r2BVDu4lWgcVW7rvp4KI6O8wcKu5+y8FSWRAns3vf5J449S8gvUCRg=
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:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=ddafvnpIocQVliuqLDmWWsvOSGw=; b=RGoPilJltpppb78PggmhMgPy2s/g
	csgAMufFOHdwlb1HSsfNNDqtFececmPBBwVvJHQ6AL4OWfsonhXkvrUkpFD26/8D
	1QgVmMegJbG0iaDqVi/KxL4rgbnEqu/6KpSYKzR0mRATywg2cHmET8q7dVVKXcbw
	CXIaBovkXEQLcQo=
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=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Tue, 14 Apr 2015 09:34:56 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin hangs up if several keys are typed during outputting a lot of texts.
Message-ID:	<20150414073456.GY7343@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<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> <20150413193100 DOT a393612bde79a4ae57b8c7d9 AT nifty DOT ne DOT jp>
MIME-Version:	1.0
In-Reply-To:	<20150413193100.a393612bde79a4ae57b8c7d9@nifty.ne.jp>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--zmbF4WfaG2f6E7cU
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Takashi,

On Apr 13 19:31, Takashi Yano wrote:
> Hi Corinna,
>=20
> I'm sorry for late reply.

No worries.

> On Tue, 7 Apr 2015 11:11:13 +0200
> Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
>=20
> > 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?
>=20
> I am considering of this issue for several days.
> However, it is still with dificulty.
>=20
> For my better understanding, may I ask a question?
>=20
> At where does cygwin set the standard output handle
> for native windows programs to fhandler_pty_slave::
> output_handle?

It doesn't.  The only way to set a handle for a native client is by
propagating the handle via execve.

And the native client, not knowing what he's talking to, recognizes the
output stream as a normal named pipe, if it's looking for that info at
all.  Being native, it will use native Windows MSVCRT stdio calls.
Worse, as you can see in the behaviour of some native applications, the
MSVCRT isatty() call returns 0 for named pipes.

If we have a Cygwin client, we can do all kinds of stuff on the slave
side, but as soon as we have a native client, only the master side of
the pty has any chance to do the right thing.  That's why I wrote that
we don't have the slave side under control.

Therefore we should really move the OPOST code back to the master side.
I'm reluctant to just revert your patch, though, because I think you
know better how to fix the OPOST code to make it work correctly on the
master side.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--zmbF4WfaG2f6E7cU
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJVLMMgAAoJEPU2Bp2uRE+ghPYP/2n2vWN8Jft4uXwu3ZX4N6RX
EPnJJAKCvz4T2WebbHtFL613hReGSRGUwMH7GWsBzJY/7ShBUhJE/wwpL40J7hCV
UIvO6dWgCZFajdiStRWb56do6K0QXu8M86vP2c2hoEfmR3LkCS+sAhFw8UaUbZ+0
yljbaKIHBeN0F2VMU9YybCmmbEkdMDv/zYBYKm9IfkO44TxIr5Yyi8xhW8sm9CDC
gssIQPjeRLPwuLL+Bp0Fxdaqs4AzRIjZI+Q5nESZ8Uc6M7iS+LayuwUD1uhMf4HT
7n400eD/18dduGwya3KqnC5Z1kvLm6cLhw/pskVhh7nYnD1jNsCUjs69kjNW5gGc
IQ9xXiGIusEup6/H/w9pyHRaNlTXxMY2z7SZ8P1bTZjlJfmwM4DjplrfASCFtasG
ji/5qXxEMhqC5n2+aNXWSbjbn9RS5B1fi0YD/1Ky4jBe9ry75u+15lKflW9mnIE5
0Orv+ByEMHQ36T9fAqWqRsS9IPeyvCr5dpYcCDwm6EUxaCymDFL0FrYOhIKz9VRA
UeCqCoEVu9mbJUMoaPJiiQrnHUvlTexIHX6zP+HeLr7llSfkeqe7Ch4gTWJDtwap
l4Bu9BztdC+BIgv7s8kUWb9ng+xyC83op1ZgMWRKZiKtDUV2X8r+NYiRlK82CdQs
pOi+y8gZ2EvEXInwXp8u
=9pzB
-----END PGP SIGNATURE-----

--zmbF4WfaG2f6E7cU--

- Raw text -