Re: Re: testing of PEAR 1.7.0 / bug found

From: Date: Tue, 27 Nov 2007 00:26:36 +0000
Subject: Re: Re: testing of PEAR 1.7.0 / bug found
References: 1 2 3 4 5 6 7 8  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-48614@lists.php.net to get a copy of this message
Travis Swicegood wrote: > On Nov 24, 2007, at 8:45 PM, Chuck Burgess wrote: > >> On Nov 24, 2007 4:11 PM, Gregory Beaver <greg@chiaraquartet.net> wrote: >> >>> >>> What freaky OS is this on? proc_open() is not returning false on trying >>> to run a non-existent file?? >>> >>> :) >>> Greg >>> >> >> If you have sigterm enabled in your PHP compilation, you cannot trust the >> return code from proc_open(). At least that's what I discovered on an >> old >> PHP bug when I was trying to figure out why the return code was crap. I >> added a user note on the PHP manual's proc_open() page about it several >> weeks ago. > > 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 ;-) Hi Travis, Check out the code in PEAR_Runtest->system_with_timeout(), it uses a PHP5+ proc_get_status call to retrieve the return code. The problem I was having with proc_open() calling a non-existent php interpreter. The other return code stuff works great. Greg

« previous php.pear.dev (#48614) next »