ID: 22844 Updated by: [EMAIL PROTECTED] Reported By: gk at proliberty dot com -Status: Open +Status: Closed Bug Type: CGI related Operating System: linux RH 7.2 PHP Version: 4.3.2-RC New Comment:
This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=On -r 'f();' 2>/dev/null Fatal error: Call to undefined function: f() in Command line code on line 1 is what I get with latest CVS meaning that the problem is indeed fixed. Previous Comments: ------------------------------------------------------------------------ [2003-03-24 17:08:19] gk at proliberty dot com This problem appears fixed only half way. This code example is a little bit subtle because there are two startup errors generated: one to STDOUT and one to STDERR. In the case of the STDERR message, the problem is fixed. But in the case of the STDOUT message, it is not: THIS WORKS: -d display_startup_errors=1 THIS DOESN'T: -d display_startup_errors=On [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=On -r 'f();' [24-Mar-2003 14:34:21] PHP Fatal error: Call to undefined function: f() in Command line code on line 1 [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=On -r 'f();' 2>/dev/null [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=1 -r 'f();' 2>/dev/null Fatal error: Call to undefined function: f() in Command line code on line 1 [EMAIL PROTECTED] php4-STABLE-200303241830]# ------------------------------------------------------------------------ [2003-03-24 13:52:27] gk at proliberty dot com This problem, as I originally posted, is more general what sniper is focusing on: it is not limited to -d option; problem is reproducible with ini_set(). Perhaps we should change the title again to: "On/Off" ini options do not work for display_error or display_startup_errors? I'm not sure if the issue applies to other options than these. sniper, have you verified the same behavior I saw with ini_set()? ------------------------------------------------------------------------ [2003-03-24 07:58:34] [EMAIL PROTECTED] Forgot to close ;) ------------------------------------------------------------------------ [2003-03-24 07:58:17] [EMAIL PROTECTED] This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2003-03-24 05:05:13] [EMAIL PROTECTED] This is actually real bug: # php -d display_errors=1 -r "f();" <-- this works # php -d display_errors=On -r "f();" <-- this is same as setting it to 0 ------------------------------------------------------------------------ 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/22844 -- Edit this bug report at http://bugs.php.net/?id=22844&edit=1
