Edit report at http://bugs.php.net/bug.php?id=52761&edit=1
ID: 52761 User updated by: freeman3 at centrum dot cz Reported by: freeman3 at centrum dot cz Summary: include backtrace in web server log on fatal error Status: Open Type: Feature/Change Request Package: Apache2 related Operating System: opensuse PHP Version: 5.3.3 Block user comment: N New Comment: Too long? I mean log only for fatal error and such. I happens only when developing application usually, few times a day. It would be few extra lines only. Access log has several GB usually so I think few lines doesn't matter. I think many developers would be grateful because this can save much time. I have tried something with shutdown handler but it didn't work for me. If you have a code that returns backtrace when fatal error occurs, I would be grateful. Previous Comments: ------------------------------------------------------------------------ [2010-09-01 18:11:05] giorgio dot liscio at email dot it i think this will marked as "wont fix" full backtrace will be too long to log.. if you want you can implement your error logger in user space ------------------------------------------------------------------------ [2010-09-01 15:21:28] freeman3 at centrum dot cz Description: ------------ is it possible to include debug backtrace in the error log when some serious error occurs? Error like "PHP Fatal error: Call to a member function getColumns() on a non-object in ../core/entity_core.php on line 230" is quite useless because I don't know from where it was called. Expected result: ---------------- Include debug backtrace in the error log Actual result: -------------- Now only the last line of backtrace is present ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=52761&edit=1
