Hi,
While trying to fix some tests, I found that display_startup_errors is
ignored by some startup errors like deprecated ini settings. Using:
php -d display_startup_errors=0 -d safe_mode=1 foo.php
a deprecated warning will be reaised. I think it is not the expected
behavior and consider that as a bug.
The problem is that we try to log the message and if not log backed
are available, we fall back to the sapi's log_message. In case of CLI,
it is a simple fprintf to STDERR. This simple patch should fix the
problem http://pastie.org/599790.
Any objection to the idea? I can adapt it to the other SAPI if
necessary as well as update the affected tests (like
putenv_err1.phpt).
Cheers,
Pierre
Hi,
While trying to fix some tests, I found that display_startup_errors is
ignored by some startup errors like deprecated ini settings. Using:php -d display_startup_errors=0 -d safe_mode=1 foo.php
See also bug #49362 (http://bugs.php.net/bug.php?id=49362)
--Jani
hi
So there is even a bug report about it. I will then commit the fix
before the next RC (tomorrow morning) If no oppositions are raised
today.
Cheers,
Hi,
While trying to fix some tests, I found that display_startup_errors is
ignored by some startup errors like deprecated ini settings. Using:php -d display_startup_errors=0 -d safe_mode=1 foo.php
See also bug #49362 (http://bugs.php.net/bug.php?id=49362)
--Jani
--
Pierre
"Jani Taskinen" jani.taskinen@iki.fi wrote in message
news:4A9BB132.6080503@iki.fi...
Hi,
While trying to fix some tests, I found that display_startup_errors is
ignored by some startup errors like deprecated ini settings. Using:php -d display_startup_errors=0 -d safe_mode=1 foo.php
See also bug #49362 (http://bugs.php.net/bug.php?id=49362)
--Jani
and also see #48583
http://bugs.php.net/bug.php?id=48583
Definitely, during startup, the errors/warnings/notices must be buffered.
They can not go directly to the error handlers.
It's because configuration (php.ini) may not be loaded and settings related
to the errors are not in effect.