php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #9384 fatal errors bypass user defined error handler
Submitted: 2001-02-21 16:21 UTC Modified: 2001-04-29 11:30 UTC
From: smaug at thegame dot com Assigned:
Status: Closed Package: Unknown/Other Function
PHP Version: 4.0.3pl1 OS: Win2K
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: smaug at thegame dot com
New email:
PHP Version: OS:

 

 [2001-02-21 16:21 UTC] smaug at thegame dot com
i don't know if this is supposed to be a feature or not... but there should be some mechanism to handle fatal errors.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-04-29 11:30 UTC] jmoore@php.net
this is the expected behaviour because we cannot verify if the zend engine is still stable after a fatal error so it shuts down. Fatal errors are fatal for a reason although there are some feature change requests to separate out Zend fatals (which will never be catchable) and PHP Fatal errors which maybe oneday we can make catchable.

- James
 [2002-01-28 02:56 UTC] flying at dom dot natm dot ru
Anyway having no way to catch fatal errors is bad for production sites, because site simple "hangs" with no response (if output buffering is turned on) or breaks all page layout with nasty message. 

 I propose you to add setting to php.ini, which will force page redirection to specified URL if fatal error occurs (if no HTTP headers is sent on a moment of fatal error occuring). It will give web developer a chance to show user a page with information, that error is occured.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Dec 06 08:01:27 2024 UTC