ID: 47918 Comment by: nobodyy at mailinator dot com Reported By: RQuadling at GMail dot com Status: Open Bug Type: Streams related Operating System: Windows PHP Version: 5.*, 6CVS (2009-06-19 New Comment:
Same problem here... If we use proc_open and the output (pipes[1]) is greater than 2kb, the application just gets stuck! I don't have any idea why, but it is never terminated, unless we do an FREAD of FGETS at the pipe[1]. But we can't do the FGETS if we don't know if there is content to be read. There is when stream_set_blocking should save the day.. But it doesn't work! :( Previous Comments: ------------------------------------------------------------------------ [2009-07-28 09:47:05] morrisdavidd at gmail dot com I tested this on PHP 5.3 (on Linux) and duplicated the error that the print_r command shows blocking as true. HOWEVER, the stream does not block when actually tested... a simple test script can be created by adding a line and slightly modifying the scripts found at: http://bugs.php.net/bug.php?id=49084 ------------------------------------------------------------------------ [2009-06-19 11:12:34] [email protected] If it exists below 5.3, the version must state it! Do NOT touch it again. ------------------------------------------------------------------------ [2009-06-19 09:31:34] RQuadling at GMail dot com Only worry about 5.3+ ------------------------------------------------------------------------ [2009-05-08 09:58:57] RQuadling at GMail dot com I also tried opening the pipes descriptors like ... $a_Descriptors = array(0 => array('pipe', 'rn'), 1 => array('pipe', 'wn'), 2 => array('pipe', 'wn')); but no change. ------------------------------------------------------------------------ [2009-04-07 21:50:45] RQuadling at GMail dot com I tried both 0 and False to set non blocking mode. In all cases the function returns false and the meta data reports that the pipe is still in blocking mode. I've just tried it with PHP 5.2.8 (cli) (built: Dec 8 2008 19:31:23) (on Windows XP SP3) on my home laptop and the same problem. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/47918 -- Edit this bug report at http://bugs.php.net/?id=47918&edit=1
