X-Spam-Check-By: sourceware.org Message-ID: X-Sender: ppchacker AT hotmail DOT com From: "PPC Hacker" To: cygwin AT cygwin DOT com Subject: Re: cygwin 1.5.18-1 + Perl + open-pipe + native executable Date: Tue, 13 Dec 2005 13:21:22 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Brian wrote: >Your test case works fine with the current CVS build of Cygwin, so >whatever was causing this has probably already been fixed. Thanks, that's good to know. I should have tried it myself. Using the snaphot 12/13/2005 build of cygwin1.dll it indeed works. Rene wrote: >>If $prog is a native windows executable and a shell isn't required >>(i.e., Perl does a direct fork/exec), the open hangs. >The open doesn't hang, it's the windows executable that keeps waiting for >input >on the pipe... and the pipe is not connected. I believe this analysis is incorrect. If you examine the Perl script in the example you will see that the call to open() never returns. Yes, the windows executable is waiting for input (on a connected pipe), but it never receives this input because the Perl script never advances past the open. For what it's worth, this "used to work", at least on a very ancient cygwin (1.5.3) / Perl (5.0.8) combination. Something along the way broke it, but as reported above, it has apparently been fixed again. Thanks for the feedback! -- Rick _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/