This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygwin 1.5.18-1 + Perl + open-pipe + native executable

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!

-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]