This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Pipes bug when spawning non-cygwin processes
- From: Edward Lam <triplequadsupport at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Feb 2020 14:24:38 -0500
- Subject: Re: Pipes bug when spawning non-cygwin processes
- References: <CAJZe6MDdZnE7BNZQWSHgaLo6sbx+9KVhG+wKfcruh_exPaZFLQ@mail.gmail.com> <20200131072536.da46ccf9cb52b1afdefa2a9a@nifty.ne.jp> <CAJZe6MDszFgBvjhga_WCaTKACk3GWbP-jBGsZ3dd-4vMrQ93iQ@mail.gmail.com>
Hi Folks,
I'm noticing a different problem with pipes that isn't fixed even in the
latest 2020-02-12 cygwin1.dll snapshot. When a native graphical Windows
process is launched (in the foreground without & in the command line) from
mintty/bash, the STARTUPINFO structure for the child Windows process
correctly has the STARTF_USESTDHANDLES bit set into info.dwFlags BUT both
info.hStdInput and info.hStdOutput handles are 0, only info.hStdError is
assigned to a handle. So in the older cygwin versions, this application's
printf() calls go out to the shell as desired but not anymore.
Any ideas?
-Edward
On Fri, Jan 31, 2020 at 1:25 AM Edward Lam <triplequadsupport@gmail.com>
wrote:
> On Thu, Jan 30, 2020 at 5:25 PM Takashi Yano <takashi.yano@nifty.ne.jp>
> wrote:
>
>> 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/
>>
>>
> Indeed, this works again after 20202401 snapshot!
>
> Thanks,
> -Edward
>
--
Support GOToronto by rating us in the App Store!
--
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