From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113404 invoked by alias); 18 Feb 2020 19:24:56 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 113385 invoked by uid 89); 18 Feb 2020 19:24:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=store!, ideas, edward, www.cygwin.com X-HELO: mail-ed1-f46.google.com Received: from mail-ed1-f46.google.com (HELO mail-ed1-f46.google.com) (209.85.208.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 18 Feb 2020 19:24:53 +0000 Received: by mail-ed1-f46.google.com with SMTP id j17so26134805edp.3 for ; Tue, 18 Feb 2020 11:24:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=vlMCqy/698paTSywMyY6Ke19Y9lDGNcyNnDzjdISZBU=; b=T/BA+vVUogS9RGljrZ9PAPLlhwtEAmx2CZZ+HmJArNTWs2c+b+cPnUdXg4Rblh0X+D ENAkcay0GK0Fr6NNibNuYf1xderpjhY3Jj/LeRWUAjA3KruidJJwwOswYp8N+6+6bYxY 3M1YtE0mTnY77XC0zy2qRDta8mrE4AB9zzLwd/PaZMFDNDa1vVoCwLkPeOouGjrBCiRD eZh6FBsUpwGSWINoIs2eCSRew1dCXfObG5Wko9C4WDeJGCPkxjWRJQJ8ZwPTQ1dGMbUM +PtZo8RoCiEifAbiQLWfnCI4cM6RRH3Fl+YnnxjbBdBKXpwa3yjQ/InuLL8T/iH9Q5Zn VPuA== MIME-Version: 1.0 References: <20200131072536.da46ccf9cb52b1afdefa2a9a@nifty.ne.jp> In-Reply-To: From: Edward Lam Date: Tue, 18 Feb 2020 19:24:00 -0000 Message-ID: Subject: Re: Pipes bug when spawning non-cygwin processes To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00139.txt.bz2 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 wrote: > On Thu, Jan 30, 2020 at 5:25 PM Takashi Yano > 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