Re: Re: testing of PEAR 1.7.0 / bug found

On Nov 26, 2007 11:23 AM, Travis Swicegood <development@domain51.com> wrote: > Is it the sigterm that does it? I ran into an issue with proc_open() not > returning an exit code properly in PHPT and ended up adding "; > echo ?>&3" to the end of my command to capture it. Of course, that killed > Windows usage, but I'm still a 0.xalpha ;-) > It's actually "sigchild", not "sigterm", so I named the culprit incorrectly from memory. Here's my User Note from the PHP manual page for *proc_open()* : It seems that if you configured --enable-sigchild when you compiled PHP (which from my reading is required for you to use Oracle stuff), then return codes from proc_close() cannot be trusted. Using proc_open's Example 1998's code on versions I have of PHP4 (4.4.7) and PHP5 (5.2.4), the return code is always "-1". This is also the only return code I can cause by running other shell commands whether they succeed or fail. I don't see this caveat mentioned anywhere except on this old bug report -- http://bugs.php.net/bug.php?id=29123 (Sorry for big font... not many options in Gmail for enlarging the tiny "normal" text pasted from the user note) -- CRB Let me introduce you to my very own DMCA-protected encryption key: BC 1B 64 4A 8D DE 49 E8 C3 7D CC EE 1A AD EE F5 (compliments of Freedom-to-Tinker http://www.freedom-to-tinker.com/?p=1155)