X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4DCAB29C.7010205@sidefx.com> Date: Wed, 11 May 2011 12:00:28 -0400 From: Edward Lam User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Who's using "CYGWIN=tty" and why? References: <20110510211800 DOT CCBDF9D5A21 AT mail2 DOT intersystems DOT com> <20110511063433 DOT GD28594 AT calimero DOT vinschen DOT de> <4DCAA510 DOT 9000909 AT sidefx DOT com> In-Reply-To: <4DCAA510.9000909@sidefx.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 5/11/2011 11:02 AM, Edward Lam wrote: > So this brings us to Cygwin. When we spawn such a Windows mode app from > Cygwin, the method I describe above fails. The call to > _open_osfhandle(info.hStdOutput, _O_TEXT) returns with an error value of > -1. This is likely why jam reports "the handle is invalid". PS. It would be interesting to find out why this fails. I would have expected that Cygwin/bash would have spawned the child process such that the inherited hStdOutput handle was open-able with _open_osfhandle(). -Edward -- 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