Edit report at https://bugs.php.net/bug.php?id=64924&edit=1
ID: 64924 User updated by: matteosistisette at gmail dot com Reported by: matteosistisette at gmail dot com Summary: 500 internal server error caused by PHP but nothing logged in error log Status: Not a bug Type: Bug Package: *Web Server problem Operating System: ubuntu 12.10 PHP Version: 5.4.15 Block user comment: N Private report: N New Comment: No man, my error hanler sends a 500 AND prints a stack trace. I've had thousands of errors in my code before, and my error handler correctly printed a stack trace. And if there was an error in my error handler, then the PHP error should be normally logged in the error_log. NOTHING is logged in the error_log, that seems to indicate PHP is crashing. No matter how bad is my error handler, if it crashes PHP there's a bug in PHP Previous Comments: ------------------------------------------------------------------------ [2013-05-27 14:44:43] ras...@php.net There is no bug. Your custom error handler is explicitly sending a 500. We do not need to see it. ------------------------------------------------------------------------ [2013-05-27 14:33:28] matteosistisette at gmail dot com spam spam spam spam spam spam spam spam spam spam spam Now my next comment will be the code, which is valuable information to fix the bug, but it won't let me post it ------------------------------------------------------------------------ [2013-05-27 14:32:29] ras...@php.net . ------------------------------------------------------------------------ [2013-05-27 14:32:15] matteosistisette at gmail dot com It's unbelievable. I can post any sort of stupid blah bla blah, but if I try to paste a snippet of code it rejects it at spam. ------------------------------------------------------------------------ [2013-05-27 14:31:30] matteosistisette at gmail dot com Good catch. It's almost certainly the error handler. However, while I try to paste the code here, this broken bugtracker keeps rejecting it as spam. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=64924 -- Edit this bug report at https://bugs.php.net/bug.php?id=64924&edit=1