This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Pipes bug when spawning non-cygwin processes
- From: Takashi Yano <takashi dot yano at nifty dot ne dot jp>
- To: cygwin at cygwin dot com
- Date: Fri, 31 Jan 2020 07:25:36 +0900
- Subject: Re: Pipes bug when spawning non-cygwin processes
- Dkim-filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 00UMPVJc028307
- References: <CAJZe6MDdZnE7BNZQWSHgaLo6sbx+9KVhG+wKfcruh_exPaZFLQ@mail.gmail.com>
On Thu, 30 Jan 2020 14:03:50 -0500
Edward Lam wrote:
> I'm getting a problem where cygwin parent processes spawning non-cygwin
> child processes no longer detect when stdin has been closed. Please see the
> sample python code at the end where I've isolated the problem. I've got
> cygwin's python2 running spawn_bar.py that popen's a native non-cygwin
> python2 running bar.py. The steps to reproduce are to run this command
> using the two files detailed at the end of this email:
>
> $ python2 spawn_bar.py
>
> On Windows 10, this command quits right away as expected when using cygwin
> 3.0.7 but hangs when using cygwin 3.1.2 (version number as reported from
> running `cygcheck -c cygwin`).
>
> Looking through the release logs, nothing sticks out except for the change
> in 3.1.0 that mentions PTY changes. However, when I originally ran into
> this, it wasn't even being done through a terminal but some background
> script.
>
> Any ideas?
Probably, this is the same issue as
https://www.cygwin.com/ml/cygwin/2020-01/msg00093.html.
Please try latest cygwin snapshot.
https://cygwin.com/snapshots/
--
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