php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #52155 Change fatal_error to fatal_error_exception
Submitted: 2010-06-23 11:10 UTC Modified: 2016-01-24 04:22 UTC
From: olamedia at gmail dot com Assigned:
Status: No Feedback Package: Scripting Engine problem
PHP Version: 5.3.2 OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: olamedia at gmail dot com
New email:
PHP Version: OS:

 

 [2010-06-23 11:10 UTC] olamedia at gmail dot com
Description:
------------
It is almost impossible now to handle fatal errors.
Of course there are exists some ways (shutdown handler or ob_start): 
http://eirikhoem.wordpress.com/2008/03/15/dying-with-grace-phps-
register_shutdown_function/
I think, that replacing message "Fatal error" with something like  
"FatalErrorException" is possible and follows use case of exceptions.



Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-06-24 07:32 UTC] olamedia at gmail dot com
Which types of "fatal errors" we can replace with throw exception (and write to 
log/mail to/show custom html):
1. out of memory - cleanup $GLOBALS and calling GC before (to free up memory)
2. compile error - when trying to include, require or eval
3. call to undefined function - that's simpler as above, like use of undefined 
variable
 [2010-09-24 20:40 UTC] boxen1com at gmail dot com
Maybe a wordpress update will help you, because wordpress have thousands bugs.... 
We had also this bug on http//www.boxen1.com, since a wordpress update, the 
wordpress works fine,
 [2011-05-06 03:13 UTC] olamedia at gmail dot com
There are about 5-10 similar bugs:
http://bugs.php.net/search.php?cmd=display&search_for=fatal&x=0&y=0

Handling fatal errors is important. Another option is to use external debugger, 
which in some cases takes a longer time (to setup copy of website locally or to 
setup connection - we not always have ssh and not always allowed to setup own 
software on shared server) than inserting exit at each script to find the place 
with loop.
 [2016-01-15 14:03 UTC] danack@php.net
-Status: Open +Status: Feedback
 [2016-01-15 14:03 UTC] danack@php.net
Most of the internal engine errors that previously gave fatal errors have been changed to use exceptions - https://wiki.php.net/rfc/engine_exceptions_for_php7

Please report any remaining problems individually.
 [2016-01-24 04:22 UTC] php-bugs at lists dot php dot net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sun Oct 17 07:03:33 2021 UTC