php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #39389 of course it would be helpfull
Submitted: 2006-11-05 16:59 UTC Modified: 2006-11-06 09:10 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: corinl at gmx dot de Assigned:
Status: Wont fix Package: Feature/Change Request
PHP Version: 5.2.0 OS: linux debian
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: corinl at gmx dot de
New email:
PHP Version: OS:

 

 [2006-11-05 16:59 UTC] corinl at gmx dot de 
Description:
------------
i assume php errors like 

--
Fatal error: Call to a member function ... on a non-object
Fatal error: Call to undefined method ...
--

don't leave php in an instable state. these errors should also be catchable by a custom error handler using E_RECOVERABLE_ERROR as it help's a lot with debugging.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-11-06 08:34 UTC] derick@php.net 
Actually, they do... and why would you want to catch that in the first place? It's a coding error which you catch while testing your code.
 [2006-11-06 09:10 UTC] corinl at gmx dot de 
well, assume you change the name of an methode. in a big project, it takes hours / days to make sure, all affected places have been adjusted. to find the missing ones you have either to get the "white page" (error page) yourself, a customer has to provide the info or you would have to look for "fatal error..." in the error logs of php. having this catchable, i could make php send me a nice email with backtrace when such an error occurs... :)

also when dealing with higly dynamic objects it could be very usefull to find logic/programming errors, which only occur in a special context. without a backtrace (with the internal php fatal error unluckily does not output), it's very hard to debug such errors.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sun Jul 13 13:01:32 2025 UTC