|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #52358 Improve error_log to be more helpful
Submitted: 2010-07-16 11:00 UTC Modified: -
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: andreas dot streichardt at globalpark dot com Assigned:
Status: Open 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.
Block user comment
Status: Assign to:
Bug Type:
From: andreas dot streichardt at globalpark dot com
New email:
PHP Version: OS:


 [2010-07-16 11:00 UTC] andreas dot streichardt at globalpark dot com
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.


Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Wed Oct 28 16:01:26 2020 UTC