#47981 [Csd]: error handler not called regardless
| From: | oliver dot graetz at gmx dot de | Date: | Thu, 16 Apr 2009 15:55:48 +0000 |
| Subject: | #47981 [Csd]: error handler not called regardless | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-135885@lists.php.net to get a copy of this message | ||
ID: 47981
User updated by: oliver dot graetz at gmx dot de
Reported By: oliver dot graetz at gmx dot de
Status: Closed
Bug Type: Scripting Engine problem
Operating System: Windows Vista x64 SP1
PHP Version: 5.2.9
Assigned To: bjori
New Comment:
If I analyzed the diffs of the last snapshots correctly, the this issue
was more esoteric the I imagined, since my test triggered the only use
of E_STRICT happening at compile time, that therefore did not use
php_error_docref().
Note to self: This problem is very loosely connected to
http://bugs.php.net/bug.php?id=41461 because the
E_STRICT is not
triggered when not implementing an (empty or non-empty) interface.
Previous Comments:
------------------------------------------------------------------------
[2009-04-16 13:56:10] bjori@php.net
This bug has been fixed in CVS.
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/.
Thank you for the report, and for helping us make PHP better.
------------------------------------------------------------------------
[2009-04-16 08:42:24] oliver dot graetz at gmx dot de
Bug system forgot to reinclude PHP version after CAPTCHA problem.
------------------------------------------------------------------------
[2009-04-16 08:39:12] oliver dot graetz at gmx dot de
Description:
------------
In the documentation of the set_error_handler it says:
It is important to remember that the standard PHP error handler is
completely bypassed. error_reporting() settings will have no effect and
your error handler will be called regardless
This is wrong! Errors of type E_STRICT will only trigger the custom
error handler function if error_reporting explicitly includes them. This
clearly means that error_reporting() settings HAVE an effect.
Personally, I think this is an error in PHP and that the behaviour of
PHP should be changed to fit the description in the documentation but
from the current point this is at least a documentation problem.
Reproduce code:
---------------
// --- file 'errorhandler.php' --------------------------------
<?php
$errormap = array(
E_WARNING=>'E_WARNING', E_NOTICE=>'E_NOTICE',
E_STRICT=>'E_STRICT'
);
function handleError($errno,$errstr,$errfile,$errline,$errcontext)
{
echo "$errno (".$GLOBALS['errormap'][$errno].": $errstr\n";
}
set_error_handler('handleError');
// --- file 'tester.php' --------------------------------------
<?php
include 'errorhandler.php';
error_reporting(E_ALL);
$x=5/0; //E_WARNING
echo $not_set; //E_NOTICE
//E_STRICT
interface a{}
class b implements a { function f($a=1) {}}
class c extends b {function f() {}}
Expected result:
----------------
2 (E_WARNING: Division by zero
8 (E_NOTICE: Undefined variable: not_set
2048 (E_STRICT: Declaration of c::f() should be compatible with that of
b::f()
Actual result:
--------------
2 (E_WARNING: Division by zero
8 (E_NOTICE: Undefined variable: not_set
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=47981&edit=1