public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Edward Lam <triplequadsupport@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Pipes bug when spawning non-cygwin processes
Date: Tue, 18 Feb 2020 19:24:00 -0000	[thread overview]
Message-ID: <CAJZe6MBh5mDzb8JDG+tG7wCq9RdU4CcxF01hNW7Qrj4JqjTZNg@mail.gmail.com> (raw)
In-Reply-To: <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

  reply	other threads:[~2020-02-18 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 19:04 Edward Lam
2020-01-30 22:25 ` Takashi Yano
2020-01-31  6:25   ` Edward Lam
2020-02-18 19:24     ` Edward Lam [this message]
2020-02-18 19:43       ` Takashi Yano
2020-02-20 19:33         ` Edward Lam
2020-02-21  1:01           ` Takashi Yano
2020-02-21  1:08             ` Takashi Yano
2020-02-21  1:23               ` Takashi Yano
2020-02-24 14:46             ` Edward Lam

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=CAJZe6MBh5mDzb8JDG+tG7wCq9RdU4CcxF01hNW7Qrj4JqjTZNg@mail.gmail.com \
    --to=triplequadsupport@gmail.com \
    --cc=cygwin@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).