From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: pty: Set input_available_event only for cygwin pipe.
Date: Tue, 19 Jan 2021 00:41:01 +0900 [thread overview]
Message-ID: <20210119004101.482327ca82eef5461b6b3e3c@nifty.ne.jp> (raw)
In-Reply-To: <20210118152700.GJ59030@calimero.vinschen.de>
On Mon, 18 Jan 2021 16:27:00 +0100
Corinna Vinschen wrote:
> On Jan 19 00:00, Takashi Yano via Cygwin-patches wrote:
> > Hi Corinna,
> >
> > On Fri, 15 Jan 2021 18:26:31 +0900
> > Takashi Yano wrote:
> > > - cat exits immediately in the following senario.
> > > 1) Execute env CYGWIN=disable_pcon script
> > > 2) Execute cmd.exe
> > > 3) Execute cat in cmd.exe.
> > > This is caused by setting input_available_event for the pipe for
> > > non-cygwin app. This patch fixes the issue.
> > > ---
> > > winsup/cygwin/fhandler_tty.cc | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/winsup/cygwin/fhandler_tty.cc b/winsup/cygwin/fhandler_tty.cc
> > > index e4993bf31..0b9901974 100644
> > > --- a/winsup/cygwin/fhandler_tty.cc
> > > +++ b/winsup/cygwin/fhandler_tty.cc
> > > @@ -394,7 +394,8 @@ fhandler_pty_master::accept_input ()
> > > }
> > > }
> > >
> > > - SetEvent (input_available_event);
> > > + if (write_to == get_output_handle ())
> > > + SetEvent (input_available_event);
> > > ReleaseMutex (input_mutex);
> > > return ret;
> > > }
> > > --
> > > 2.30.0
> > >
> >
> > I would be happy if you could review this patch as well.
>
> Sorry, I missed that one! Pushed.
Thanks!
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2021-01-18 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 9:26 Takashi Yano
2021-01-18 15:00 ` Takashi Yano
2021-01-18 15:27 ` Corinna Vinschen
2021-01-18 15:41 ` Takashi Yano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210119004101.482327ca82eef5461b6b3e3c@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).