Req #52358 [Opn]: Improve error_log to be more helpful

Edit report at https://bugs.php.net/bug.php?id=52358&edit=1 ID: 52358 Updated by: cmb@php.net Reported by: andreas dot streichardt at globalpark dot com Summary: Improve error_log to be more helpful Status: Open Type: Feature/Change Request Package: Scripting Engine problem PHP Version: 5.3.2 Block user comment: N Private report: N New Comment: The problem here is that doing more processing after memory_limit was hit is likely going to require more memory. This is why this condition doesn't throw an Exception, but is a fatal error. Previous Comments: ------------------------------------------------------------------------ [2021-03-14 14:26:38] olafvdspek at gmail dot com A stack trace, like no uncaught exceptions, would certainly be nice. ------------------------------------------------------------------------ [2010-07-16 11:00:42] andreas dot streichardt at globalpark dot com Description: ------------ The error_log isn't really helpful in many cases when analyzing it. We have a very large application with memory_limits enabled and see memory_limit problems in some cases. This might be intended (misuse of the software, driving it at its limits) or an indicator of a bug. However i can't see wether it is case a) or b): PHP Fatal error: Allowed memory size of XXX bytes exhausted (tried to allocate XX bytes) in (some random file) on line XX "some random file" might give me a hint what the user was doing but in many cases there are framework/infrastructure files involved in this is not at all helpful. What would be helpful would be a stack trace or the request variables involved in the call (which might get huge on the downside). Expected result: ---------------- PHPs error logs should be helpful in most cases. Actual result: -------------- Hard fatal errors in the error_log are not helpful at all. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=52358&edit=1