#48969 [Asn]: register_shutdown_function() buggy in combination with set_error_handler()

ID: 48969 Updated by: jani@php.net Reported By: bschussek at gmail dot com Status: Assigned Bug Type: Scripting Engine problem Operating System: Linux Ubuntu 9.04 PHP Version: 5.2.10 Assigned To: dmitry New Comment: One more thing: The shutdown func WILL be run. As long as there are no uncaught exceptions left. Previous Comments: ------------------------------------------------------------------------ [2009-07-21 12:46:13] jani@php.net See also bug #30266 for which this fix was added. Commit log mentions a possibility of throwing E_FATAL error for this but leaves that to be discussed. I guess it was never discussed. :) ------------------------------------------------------------------------ [2009-07-21 12:43:38] jani@php.net It's not really buggy, you just can't call user functions when there are uncatched exceptions thrown. Comment in sources say it would otherwise cause instable executor. So instead of crashing, it just won't run your function. :) ------------------------------------------------------------------------ [2009-07-20 11:43:33] bschussek at gmail dot com In reply to Jani: Of course fatal errors are fatal, but my registered error handler should run after the warning, BEFORE the fatal error. If you replace the code throw new Exception('my exception'); with trigger_error(...); instead, you will see that the custom error is triggered correctly. The same is not the case for exceptions. ------------------------------------------------------------------------ [2009-07-20 11:12:34] derick@php.net I am reopening this. Because even with fatal errors, the shutdown handler should run. It always has so if that changes it is a BC break. Assigning to Dmitry. ------------------------------------------------------------------------ [2009-07-20 10:57:29] jani@php.net FATAL errors are fatal, the execution of the scripts ends at those. No bug here. ------------------------------------------------------------------------ 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/48969 -- Edit this bug report at http://bugs.php.net/?id=48969&edit=1