How do I catch a PHP fatal E ERROR error

Question

I can use set error handler   to catch most PHP errors  but it doesn t work for fatal  E ERROR  errors  such as calling a function that doesn t exist  Is there another way to catch these errors   I am trying to call mail   for all errors and am running PHP 5 2 3

User · Answer

Since most answers here are unnecesarily verbose  here s my non-ugly version of the top voted answer   function errorHandler  errno   errstr   errfile        errline   0   errcontext   array            Do stuff  mail  log  etc    function fatalHandler          error   error get last        if  error  errorHandler  error  type     error  message     error  file     error  line        set error handler  errorHandler   register shutdown function  fatalHandler

User · Answer

PHP doesn t provide conventional means for catching and recovering from fatal errors  This is because processing should not typically be recovered after a fatal error  String matching an output buffer  as suggested by the original post the technique described on PHP net  is definitely ill-advised  It s simply unreliable   Calling the mail   function from within an error handler method prove to be problematic  too  If you had a lot of errors  your mail server would be loaded with work  and you could find yourself with a gnarly inbox  To avoid this  you might consider running a cron to scan error logs periodically and send notifications accordingly  You might also like to look into system monitoring software  such as Nagios     To speak to the bit about registering a shutdown function   It s true that you can register a shutdown function  and that s a good answer   The point here is that we typically shouldn t try to recover from fatal errors  especially not by using a regular expression against your output buffer  I was responding to the accepted answer  which linked to a suggestion on php net which has since been changed or removed   That suggestion was to use a regex against the output buffer during exception handling  and in the case of a fatal error  detected by the matching against whatever configured error text you might be expecting   try to do some sort of recovery or continued processing  That would not be a recommended practice  I believe that s why I can t find the original suggestion  too  I m either overlooking it  or the php community shot it down    It might be worth noting that the more recent versions of PHP  around 5 1  seem to call the shutdown function earlier  before the output buffering callback is envoked   In version 5 and earlier  that order was the reverse  the output buffering callback was followed by the shutdown function   Also  since about 5 0 5  which is much earlier than the questioner s version 5 2 3   objects are unloaded well before a registered shutdown function is called  so you won t be able to rely on your in-memory objects to do much of anything   So registering a shutdown function is fine  but the sort of tasks that ought to be performed by a shutdown function are probably limited to a handful of gentle shutdown procedures   The key take-away here is just some words of wisdom for anyone who stumbles upon this question and sees the advice in the originally accepted answer  Don t regex your output buffer

User · Answer

Not really  Fatal errors are called that  because they are fatal  You can t recover from them

User · Answer

You can t catch handle fatal errors  but you can log report them  For quick debugging I modified one answer to this simple code  function   fatalHandler          error   error get last            Check if it s a core fatal error  otherwise it s a normal shutdown     if   error     NULL  amp  amp  in array  error  type            array E ERROR  E PARSE  E CORE ERROR  E CORE WARNING                E COMPILE ERROR  E COMPILE WARNING E RECOVERABLE ERROR               echo   lt pre gt fatal error  n           print r  error           echo   lt  pre gt            die           register shutdown function    fatalHandler

User · Answer

I need to handle fatal errors for production to instead show a static styled 503 Service Unavailable HTML output  This is surely a reasonable approach to  catching fatal errors   This is what I ve done   I have a custom error handling function  error handler  which will display my  503 service unavailable  HTML page on any E ERROR  E USER ERROR  etc  This will now be called on the shutdown function  catching my fatal error   function fatal error handler          if   is array  e    error get last                code   isset  e  type       e  type     0           msg   isset  e  message       e  message                  file   isset  e  file       e  file                  line   isset  e  line       e  line                 if   code gt 0              error handler  code   msg   file   line           set error handler  error handler    register shutdown function  fatal error handler      in my custom error handler function  if the error is E ERROR  E USER ERROR  etc  I also call  ob end clean    to empty the buffer  thus removing PHP s  fatal error  message   Take important note of the strict isset   checking and   silencing functions since we don   t want our error handler scripts to generate any errors   In still agreeing with keparo  catching fatal errors does defeat the purpose of  FATAL error  so it s not really intended for you to do further processing  Do not run any mail   functions in this shutdown process as you will certainly back up the mail server or your inbox  Rather log these occurrences to file and schedule a cron job to find these error log files and mail them to administrators

User · Answer

I developed this function to make it possible to  sandbox  code that could cause a fatal error  Since exceptions thrown from the closure register shutdown function don t get emitted from the pre-fatal error call stack  I m forced to exit after this function to provide a uniform way of using it   function superTryCatchFinallyAndExit  Closure  try  Closure  catch   NULL  Closure  finally          finished   FALSE      register shutdown function  function   use    amp  finished   catch   finally             if     finished                  finished   TRUE              print  EXPLODE   PHP EOL              if   catch                     superTryCatchFinallyAndExit  function   use    catch                          catch  new Exception   Fatal Error                             NULL   finally                                  else                    finally                                                         try            try          catch  Exception  e             if   catch                 try                    catch   e                  catch  Exception  e                           finished   TRUE       finally        exit

User · Answer

Since most answers here are unnecesarily verbose  here s my non-ugly version of the top voted answer   function errorHandler  errno   errstr   errfile        errline   0   errcontext   array            Do stuff  mail  log  etc    function fatalHandler          error   error get last        if  error  errorHandler  error  type     error  message     error  file     error  line        set error handler  errorHandler   register shutdown function  fatalHandler

User · Answer

I need to handle fatal errors for production to instead show a static styled 503 Service Unavailable HTML output  This is surely a reasonable approach to  catching fatal errors   This is what I ve done   I have a custom error handling function  error handler  which will display my  503 service unavailable  HTML page on any E ERROR  E USER ERROR  etc  This will now be called on the shutdown function  catching my fatal error   function fatal error handler          if   is array  e    error get last                code   isset  e  type       e  type     0           msg   isset  e  message       e  message                  file   isset  e  file       e  file                  line   isset  e  line       e  line                 if   code gt 0              error handler  code   msg   file   line           set error handler  error handler    register shutdown function  fatal error handler      in my custom error handler function  if the error is E ERROR  E USER ERROR  etc  I also call  ob end clean    to empty the buffer  thus removing PHP s  fatal error  message   Take important note of the strict isset   checking and   silencing functions since we don   t want our error handler scripts to generate any errors   In still agreeing with keparo  catching fatal errors does defeat the purpose of  FATAL error  so it s not really intended for you to do further processing  Do not run any mail   functions in this shutdown process as you will certainly back up the mail server or your inbox  Rather log these occurrences to file and schedule a cron job to find these error log files and mail them to administrators

User · Answer

PHP has catchable fatal errors  They are defined as E RECOVERABLE ERROR  The PHP manual describes an E RECOVERABLE ERROR as      Catchable fatal error  It indicates that a probably dangerous error occured  but did not leave the Engine in an unstable state  If the error is not caught by a user defined handle  see also set error handler     the application aborts as it was an E ERROR    You can  catch  these  fatal  errors by using set error handler   and checking for E RECOVERABLE ERROR  I find it useful to throw an Exception when this error is caught  then you can use try catch   This question and answer provides a useful example  How can I catch a  quot catchable fatal error quot  on PHP type hinting   E ERROR errors  however  can be handled  but not recovered from as the engine is in an unstable state

User · Answer

PHP doesn t provide conventional means for catching and recovering from fatal errors  This is because processing should not typically be recovered after a fatal error  String matching an output buffer  as suggested by the original post the technique described on PHP net  is definitely ill-advised  It s simply unreliable   Calling the mail   function from within an error handler method prove to be problematic  too  If you had a lot of errors  your mail server would be loaded with work  and you could find yourself with a gnarly inbox  To avoid this  you might consider running a cron to scan error logs periodically and send notifications accordingly  You might also like to look into system monitoring software  such as Nagios     To speak to the bit about registering a shutdown function   It s true that you can register a shutdown function  and that s a good answer   The point here is that we typically shouldn t try to recover from fatal errors  especially not by using a regular expression against your output buffer  I was responding to the accepted answer  which linked to a suggestion on php net which has since been changed or removed   That suggestion was to use a regex against the output buffer during exception handling  and in the case of a fatal error  detected by the matching against whatever configured error text you might be expecting   try to do some sort of recovery or continued processing  That would not be a recommended practice  I believe that s why I can t find the original suggestion  too  I m either overlooking it  or the php community shot it down    It might be worth noting that the more recent versions of PHP  around 5 1  seem to call the shutdown function earlier  before the output buffering callback is envoked   In version 5 and earlier  that order was the reverse  the output buffering callback was followed by the shutdown function   Also  since about 5 0 5  which is much earlier than the questioner s version 5 2 3   objects are unloaded well before a registered shutdown function is called  so you won t be able to rely on your in-memory objects to do much of anything   So registering a shutdown function is fine  but the sort of tasks that ought to be performed by a shutdown function are probably limited to a handful of gentle shutdown procedures   The key take-away here is just some words of wisdom for anyone who stumbles upon this question and sees the advice in the originally accepted answer  Don t regex your output buffer

User · Answer

There are certain circumstances in which even fatal errors should be caught  you might need to do some clean up before exiting gracefully and don   t just die      I have implemented a pre system hook in my CodeIgniter applications so that I can get my fatal errors through emails  and this helped me finding bugs that were not reported  or were reported after they were fixed  as I already knew about them       Sendemail checks if the error has already been reported so that it does not spam you with known errors multiple times   class PHPFatalError        public function setHandler             register shutdown function  handleShutdown             function handleShutdown         if    error   error get last               ob start            echo   lt pre gt            var dump  error           echo   lt  pre gt             message   ob get clean            sendEmail  message           ob start            echo    status   error   message   Internal application error              ob flush            exit

User · Answer

I just came up with this solution  PHP 5 2 0     function shutDownFunction          error   error get last            Fatal error  E ERROR     1     if   error  type       E ERROR                Do your stuff         register shutdown function  shutDownFunction      Different error types are defined at Predefined Constants

User · Answer

You cannot throw an exception inside a registered shutdown function like that    lt  php     function shutdown             if    error   error get last                  ob clean               throw new Exception  fatal error                         try            x   null           x- gt method         catch Exception  e              This won t work         gt    But you can capture and redirect request to another page    lt  php     function shutdown             if    error   error get last                  ob clean                 Report the event  send email  etc             header  Location  http   localhost error-capture                 From  error-capture  You can use another              redirect  to e g  the home page                     register shutdown function  shutdown          x   null       x- gt method     gt

User · Answer

Well  it seems possible to catch fatal errors some other way     ob start  fatal error handler     function fatal error handler  buffer        error   error get last        if  error  type      1              Type  message  file  line          newBuffer   lt html gt  lt header gt  lt title gt Fatal Error  lt  title gt  lt  header gt                         lt style gt                       error content                          background  ghostwhite                          vertical-align  middle                          margin 0 auto                          padding  10px                          width  50                                                error content label color  red font-family  Georgia font-size  16pt font-style  italic                         error content ul li  background  none repeat scroll 0 0 FloralWhite                                  border  1px solid AliceBlue                                  display  block                                  font-family  monospace                                  padding  2                                   text-align  left                                                 lt  style gt                         lt body style  text-align  center   gt                           lt div class  error content  gt                                lt label  gt Fatal Error  lt  label gt                                lt ul gt                                  lt li gt  lt b gt Line lt  b gt       error  line       lt  li gt                                  lt li gt  lt b gt Message lt  b gt       error  message       lt  li gt                                  lt li gt  lt b gt File lt  b gt       error  file       lt  li gt                                lt  ul gt                                 lt a href  javascript history back    gt  Back  lt  a gt                           lt  div gt                         lt  body gt  lt  html gt             return  newBuffer            return  buffer

User · Answer

Nice solution found in Zend Framework 2          ErrorHandler that can be used to catch internal PHP errors    and convert to an ErrorException instance      abstract class ErrorHandler                  Active stack                var array             protected static  stack   array                    Check if this error handler is active                return bool             public static function started                 return  bool  static  getNestedLevel                          Get the current nested level                return int             public static function getNestedLevel                 return count static   stack                         Starting the error handler                param int  errorLevel             public static function start  errorLevel    E WARNING                if   static   stack                set error handler array get called class     addError     errorLevel                      static   stack     null                        Stopping the error handler                param  bool  throw Throw the ErrorException if any         return null ErrorException         throws ErrorException If an error has been catched and  throw is true             public static function stop  throw   false                 errorException   null           if  static   stack                 errorException   array pop static   stack                if   static   stack                    restore error handler                               if   errorException  amp  amp   throw                    throw  errorException                                   return  errorException                        Stop all active handler                return void             public static function clean                 if  static   stack                restore error handler                       static   stack   array                          Add an error to the stack                param int     errno         param string  errstr         param string  errfile         param int     errline         return void             public static function addError  errno   errstr        errfile        errline   0                 stack    amp  static   stack count static   stack  - 1            stack   new ErrorException  errstr  0   errno   errfile   errline   stack             This class allows you to start the specific ErrorHandler sometimes if you need it  And then you can also stop the Handler   Use this class e g  like this   ErrorHandler  start E WARNING    return   call function raises E WARNING     if   innerException   ErrorHandler  stop          throw new Exception  Special Exception Text   0   innerException         or ErrorHandler  stop true      directly throws an Exception    Link to the full class code  https   github com zendframework zf2 blob master library Zend Stdlib ErrorHandler php  A maybe better solution is that one from Monolog  Link to the full class code  https   github com Seldaek monolog blob master src Monolog ErrorHandler php  It can also handle FATAL ERRORS using the register shutdown function function  According to this class a FATAL ERROR is one of the following array E ERROR  E PARSE  E CORE ERROR  E COMPILE ERROR  E USER ERROR    class ErrorHandler                     public function registerExceptionHandler  level   null   callPrevious   true                 prev   set exception handler array  this   handleException              this- gt uncaughtExceptionLevel    level          if   callPrevious  amp  amp   prev                 this- gt previousExceptionHandler    prev                       public function registerErrorHandler array  levelMap   array     callPrevious   true   errorTypes   -1                 prev   set error handler array  this   handleError     errorTypes            this- gt errorLevelMap   array replace  this- gt defaultErrorLevelMap     levelMap           if   callPrevious                 this- gt previousErrorHandler    prev    true                       public function registerFatalHandler  level   null   reservedMemorySize   20                register shutdown function array  this   handleFatalError               this- gt reservedMemory   str repeat      1024    reservedMemorySize            this- gt fatalLevel    level

User · Answer

PHP doesn t provide conventional means for catching and recovering from fatal errors  This is because processing should not typically be recovered after a fatal error  String matching an output buffer  as suggested by the original post the technique described on PHP net  is definitely ill-advised  It s simply unreliable   Calling the mail   function from within an error handler method prove to be problematic  too  If you had a lot of errors  your mail server would be loaded with work  and you could find yourself with a gnarly inbox  To avoid this  you might consider running a cron to scan error logs periodically and send notifications accordingly  You might also like to look into system monitoring software  such as Nagios     To speak to the bit about registering a shutdown function   It s true that you can register a shutdown function  and that s a good answer   The point here is that we typically shouldn t try to recover from fatal errors  especially not by using a regular expression against your output buffer  I was responding to the accepted answer  which linked to a suggestion on php net which has since been changed or removed   That suggestion was to use a regex against the output buffer during exception handling  and in the case of a fatal error  detected by the matching against whatever configured error text you might be expecting   try to do some sort of recovery or continued processing  That would not be a recommended practice  I believe that s why I can t find the original suggestion  too  I m either overlooking it  or the php community shot it down    It might be worth noting that the more recent versions of PHP  around 5 1  seem to call the shutdown function earlier  before the output buffering callback is envoked   In version 5 and earlier  that order was the reverse  the output buffering callback was followed by the shutdown function   Also  since about 5 0 5  which is much earlier than the questioner s version 5 2 3   objects are unloaded well before a registered shutdown function is called  so you won t be able to rely on your in-memory objects to do much of anything   So registering a shutdown function is fine  but the sort of tasks that ought to be performed by a shutdown function are probably limited to a handful of gentle shutdown procedures   The key take-away here is just some words of wisdom for anyone who stumbles upon this question and sees the advice in the originally accepted answer  Don t regex your output buffer

User · Answer

There are certain circumstances in which even fatal errors should be caught  you might need to do some clean up before exiting gracefully and don   t just die      I have implemented a pre system hook in my CodeIgniter applications so that I can get my fatal errors through emails  and this helped me finding bugs that were not reported  or were reported after they were fixed  as I already knew about them       Sendemail checks if the error has already been reported so that it does not spam you with known errors multiple times   class PHPFatalError        public function setHandler             register shutdown function  handleShutdown             function handleShutdown         if    error   error get last               ob start            echo   lt pre gt            var dump  error           echo   lt  pre gt             message   ob get clean            sendEmail  message           ob start            echo    status   error   message   Internal application error              ob flush            exit

User · Answer

PHP doesn t provide conventional means for catching and recovering from fatal errors  This is because processing should not typically be recovered after a fatal error  String matching an output buffer  as suggested by the original post the technique described on PHP net  is definitely ill-advised  It s simply unreliable   Calling the mail   function from within an error handler method prove to be problematic  too  If you had a lot of errors  your mail server would be loaded with work  and you could find yourself with a gnarly inbox  To avoid this  you might consider running a cron to scan error logs periodically and send notifications accordingly  You might also like to look into system monitoring software  such as Nagios     To speak to the bit about registering a shutdown function   It s true that you can register a shutdown function  and that s a good answer   The point here is that we typically shouldn t try to recover from fatal errors  especially not by using a regular expression against your output buffer  I was responding to the accepted answer  which linked to a suggestion on php net which has since been changed or removed   That suggestion was to use a regex against the output buffer during exception handling  and in the case of a fatal error  detected by the matching against whatever configured error text you might be expecting   try to do some sort of recovery or continued processing  That would not be a recommended practice  I believe that s why I can t find the original suggestion  too  I m either overlooking it  or the php community shot it down    It might be worth noting that the more recent versions of PHP  around 5 1  seem to call the shutdown function earlier  before the output buffering callback is envoked   In version 5 and earlier  that order was the reverse  the output buffering callback was followed by the shutdown function   Also  since about 5 0 5  which is much earlier than the questioner s version 5 2 3   objects are unloaded well before a registered shutdown function is called  so you won t be able to rely on your in-memory objects to do much of anything   So registering a shutdown function is fine  but the sort of tasks that ought to be performed by a shutdown function are probably limited to a handful of gentle shutdown procedures   The key take-away here is just some words of wisdom for anyone who stumbles upon this question and sees the advice in the originally accepted answer  Don t regex your output buffer

User · Answer

Not really  Fatal errors are called that  because they are fatal  You can t recover from them

User · Answer

Fatal errors or recoverable fatal errors now throw instances of Error in PHP 7 or higher versions  Like any other exceptions  Error objects can be caught using a try catch block   Example    lt  php  variable    not an object    try        variable- gt method       Throws an Error object in PHP 7 or higger    catch  Error  e           Handle error     echo  e- gt getMessage       Call to a member function method   on string     https   3v4l org 67vbk  Or you can use Throwable interface to catch all exceptions   Example    lt  php     try           undefinedFunctionCall          catch  Throwable  e               Handle error         echo  e- gt getMessage       Call to undefined function undefinedFunctionCall           https   3v4l org Br0MG  For more information  http   php net manual en language errors php7 php

User · Answer

Fatal errors or recoverable fatal errors now throw instances of Error in PHP 7 or higher versions  Like any other exceptions  Error objects can be caught using a try catch block   Example    lt  php  variable    not an object    try        variable- gt method       Throws an Error object in PHP 7 or higger    catch  Error  e           Handle error     echo  e- gt getMessage       Call to a member function method   on string     https   3v4l org 67vbk  Or you can use Throwable interface to catch all exceptions   Example    lt  php     try           undefinedFunctionCall          catch  Throwable  e               Handle error         echo  e- gt getMessage       Call to undefined function undefinedFunctionCall           https   3v4l org Br0MG  For more information  http   php net manual en language errors php7 php

User · Answer

If you are using PHP    5 1 0 Just do something like this with the ErrorException class    lt  php        Define an error handler     function exception error handler  errno   errstr   errfile   errline             throw new ErrorException  errstr   errno  0   errfile   errline                 Set your error handler     set error handler  exception error handler            Trigger exception        try                  Try to do something like finding the end of the internet           catch ErrorException  e                   Anything you want to do with  e         gt

User · Answer

I developed this function to make it possible to  sandbox  code that could cause a fatal error  Since exceptions thrown from the closure register shutdown function don t get emitted from the pre-fatal error call stack  I m forced to exit after this function to provide a uniform way of using it   function superTryCatchFinallyAndExit  Closure  try  Closure  catch   NULL  Closure  finally          finished   FALSE      register shutdown function  function   use    amp  finished   catch   finally             if     finished                  finished   TRUE              print  EXPLODE   PHP EOL              if   catch                     superTryCatchFinallyAndExit  function   use    catch                          catch  new Exception   Fatal Error                             NULL   finally                                  else                    finally                                                         try            try          catch  Exception  e             if   catch                 try                    catch   e                  catch  Exception  e                           finished   TRUE       finally        exit

User · Answer

Not really  Fatal errors are called that  because they are fatal  You can t recover from them

User · Answer

Log fatal errors using the register shutdown function  which requires PHP 5 2    register shutdown function   fatal handler      function fatal handler          errfile    unknown file        errstr     shutdown        errno     E CORE ERROR       errline   0        error   error get last         if  error     NULL             errno      error  type             errfile    error  file             errline    error  line             errstr     error  message             error mail format error   errno   errstr   errfile   errline              You will have to define the error mail and format error functions  For example   function format error   errno   errstr   errfile   errline          trace   print r  debug backtrace  false    true          content          lt table gt           lt thead gt  lt th gt Item lt  th gt  lt th gt Description lt  th gt  lt  thead gt           lt tbody gt               lt tr gt                   lt th gt Error lt  th gt                   lt td gt  lt pre gt  errstr lt  pre gt  lt  td gt               lt  tr gt               lt tr gt                   lt th gt Errno lt  th gt                   lt td gt  lt pre gt  errno lt  pre gt  lt  td gt               lt  tr gt               lt tr gt                   lt th gt File lt  th gt                   lt td gt  errfile lt  td gt               lt  tr gt               lt tr gt                   lt th gt Line lt  th gt                   lt td gt  errline lt  td gt               lt  tr gt               lt tr gt                   lt th gt Trace lt  th gt                   lt td gt  lt pre gt  trace lt  pre gt  lt  td gt               lt  tr gt           lt  tbody gt       lt  table gt        return  content      Use Swift Mailer to write the error mail function   See also     php errormsg Predefined Constants

User · Answer

Here is just a nice trick to get the current error handler method      lt  php     register shutdown function    fatalHandler         function   fatalHandler                  error   error get last                Check if it s a core fatal error  Otherwise  it s a normal shutdown         if  error     NULL  amp  amp   error  type       E ERROR                    It is a bit hackish  but the set exception handler                will return the old handler             function fakeHandler                     handler   set exception handler  fakeHandler                restore exception handler                if  handler     null                    call user func                       handler                      new ErrorException                           error  message                             error  type                            0                           error  file                             error  line                                exit                    gt    Also I want to note that if you call   lt  php     ini set  display errors   false     gt    PHP stops displaying the error  Otherwise  the error text will be send to the client prior to your error handler

User · Answer

Nice solution found in Zend Framework 2          ErrorHandler that can be used to catch internal PHP errors    and convert to an ErrorException instance      abstract class ErrorHandler                  Active stack                var array             protected static  stack   array                    Check if this error handler is active                return bool             public static function started                 return  bool  static  getNestedLevel                          Get the current nested level                return int             public static function getNestedLevel                 return count static   stack                         Starting the error handler                param int  errorLevel             public static function start  errorLevel    E WARNING                if   static   stack                set error handler array get called class     addError     errorLevel                      static   stack     null                        Stopping the error handler                param  bool  throw Throw the ErrorException if any         return null ErrorException         throws ErrorException If an error has been catched and  throw is true             public static function stop  throw   false                 errorException   null           if  static   stack                 errorException   array pop static   stack                if   static   stack                    restore error handler                               if   errorException  amp  amp   throw                    throw  errorException                                   return  errorException                        Stop all active handler                return void             public static function clean                 if  static   stack                restore error handler                       static   stack   array                          Add an error to the stack                param int     errno         param string  errstr         param string  errfile         param int     errline         return void             public static function addError  errno   errstr        errfile        errline   0                 stack    amp  static   stack count static   stack  - 1            stack   new ErrorException  errstr  0   errno   errfile   errline   stack             This class allows you to start the specific ErrorHandler sometimes if you need it  And then you can also stop the Handler   Use this class e g  like this   ErrorHandler  start E WARNING    return   call function raises E WARNING     if   innerException   ErrorHandler  stop          throw new Exception  Special Exception Text   0   innerException         or ErrorHandler  stop true      directly throws an Exception    Link to the full class code  https   github com zendframework zf2 blob master library Zend Stdlib ErrorHandler php  A maybe better solution is that one from Monolog  Link to the full class code  https   github com Seldaek monolog blob master src Monolog ErrorHandler php  It can also handle FATAL ERRORS using the register shutdown function function  According to this class a FATAL ERROR is one of the following array E ERROR  E PARSE  E CORE ERROR  E COMPILE ERROR  E USER ERROR    class ErrorHandler                     public function registerExceptionHandler  level   null   callPrevious   true                 prev   set exception handler array  this   handleException              this- gt uncaughtExceptionLevel    level          if   callPrevious  amp  amp   prev                 this- gt previousExceptionHandler    prev                       public function registerErrorHandler array  levelMap   array     callPrevious   true   errorTypes   -1                 prev   set error handler array  this   handleError     errorTypes            this- gt errorLevelMap   array replace  this- gt defaultErrorLevelMap     levelMap           if   callPrevious                 this- gt previousErrorHandler    prev    true                       public function registerFatalHandler  level   null   reservedMemorySize   20                register shutdown function array  this   handleFatalError               this- gt reservedMemory   str repeat      1024    reservedMemorySize            this- gt fatalLevel    level

User · Answer

I just came up with this solution  PHP 5 2 0     function shutDownFunction          error   error get last            Fatal error  E ERROR     1     if   error  type       E ERROR                Do your stuff         register shutdown function  shutDownFunction      Different error types are defined at Predefined Constants

User · Answer

Log fatal errors using the register shutdown function  which requires PHP 5 2    register shutdown function   fatal handler      function fatal handler          errfile    unknown file        errstr     shutdown        errno     E CORE ERROR       errline   0        error   error get last         if  error     NULL             errno      error  type             errfile    error  file             errline    error  line             errstr     error  message             error mail format error   errno   errstr   errfile   errline              You will have to define the error mail and format error functions  For example   function format error   errno   errstr   errfile   errline          trace   print r  debug backtrace  false    true          content          lt table gt           lt thead gt  lt th gt Item lt  th gt  lt th gt Description lt  th gt  lt  thead gt           lt tbody gt               lt tr gt                   lt th gt Error lt  th gt                   lt td gt  lt pre gt  errstr lt  pre gt  lt  td gt               lt  tr gt               lt tr gt                   lt th gt Errno lt  th gt                   lt td gt  lt pre gt  errno lt  pre gt  lt  td gt               lt  tr gt               lt tr gt                   lt th gt File lt  th gt                   lt td gt  errfile lt  td gt               lt  tr gt               lt tr gt                   lt th gt Line lt  th gt                   lt td gt  errline lt  td gt               lt  tr gt               lt tr gt                   lt th gt Trace lt  th gt                   lt td gt  lt pre gt  trace lt  pre gt  lt  td gt               lt  tr gt           lt  tbody gt       lt  table gt        return  content      Use Swift Mailer to write the error mail function   See also     php errormsg Predefined Constants

User · Answer

You cannot throw an exception inside a registered shutdown function like that    lt  php     function shutdown             if    error   error get last                  ob clean               throw new Exception  fatal error                         try            x   null           x- gt method         catch Exception  e              This won t work         gt    But you can capture and redirect request to another page    lt  php     function shutdown             if    error   error get last                  ob clean                 Report the event  send email  etc             header  Location  http   localhost error-capture                 From  error-capture  You can use another              redirect  to e g  the home page                     register shutdown function  shutdown          x   null       x- gt method     gt

User · Answer

PHP has catchable fatal errors  They are defined as E RECOVERABLE ERROR  The PHP manual describes an E RECOVERABLE ERROR as      Catchable fatal error  It indicates that a probably dangerous error occured  but did not leave the Engine in an unstable state  If the error is not caught by a user defined handle  see also set error handler     the application aborts as it was an E ERROR    You can  catch  these  fatal  errors by using set error handler   and checking for E RECOVERABLE ERROR  I find it useful to throw an Exception when this error is caught  then you can use try catch   This question and answer provides a useful example  How can I catch a  quot catchable fatal error quot  on PHP type hinting   E ERROR errors  however  can be handled  but not recovered from as the engine is in an unstable state

User · Answer

I developed a way to catch all error types in PHP  almost all   I have no sure about E CORE ERROR  I think will not works only for that error   But  for other fatal errors  E ERROR  E PARSE  E COMPILE     works fine using only one error handler function  There goes my solution   Put this following code on your main file  index php     lt  php     define  E FATAL    E ERROR   E USER ERROR   E PARSE   E CORE ERROR               E COMPILE ERROR   E RECOVERABLE ERROR        define  ENV    dev            Custom error handling vars     define  DISPLAY ERRORS   TRUE       define  ERROR REPORTING   E ALL   E STRICT       define  LOG ERRORS   TRUE        register shutdown function  shut         set error handler  handler            Function to catch no user error handler function errors        function shut              error   error get last             if  error  amp  amp    error  type    amp  E FATAL                handler  error  type     error  message     error  file     error  line                           function handler   errno   errstr   errfile   errline              switch   errno                case E ERROR     1                     typestr    E ERROR   break              case E WARNING     2                     typestr    E WARNING   break              case E PARSE     4                     typestr    E PARSE   break              case E NOTICE     8                     typestr    E NOTICE   break              case E CORE ERROR     16                     typestr    E CORE ERROR   break              case E CORE WARNING     32                     typestr    E CORE WARNING   break              case E COMPILE ERROR     64                     typestr    E COMPILE ERROR   break              case E CORE WARNING     128                     typestr    E COMPILE WARNING   break              case E USER ERROR     256                     typestr    E USER ERROR   break              case E USER WARNING     512                     typestr    E USER WARNING   break              case E USER NOTICE     1024                     typestr    E USER NOTICE   break              case E STRICT     2048                     typestr    E STRICT   break              case E RECOVERABLE ERROR     4096                     typestr    E RECOVERABLE ERROR   break              case E DEPRECATED     8192                     typestr    E DEPRECATED   break              case E USER DEPRECATED     16384                     typestr    E USER DEPRECATED   break                      message                 lt b gt      typestr                   lt  b gt      errstr                 in  lt b gt      errfile                 lt  b gt  on line  lt b gt      errline                 lt  b gt  lt br  gt             if   errno  amp  E FATAL   amp  amp  ENV      production                 header  Location  500 html                header  Status  500 Internal Server Error                        if    errno  amp  ERROR REPORTING               return           if DISPLAY ERRORS              printf   s    message              Logging error on php file error log            if LOG ERRORS              error log strip tags  message   0              ob start          include  content php        ob end flush      gt

User · Answer

I developed a way to catch all error types in PHP  almost all   I have no sure about E CORE ERROR  I think will not works only for that error   But  for other fatal errors  E ERROR  E PARSE  E COMPILE     works fine using only one error handler function  There goes my solution   Put this following code on your main file  index php     lt  php     define  E FATAL    E ERROR   E USER ERROR   E PARSE   E CORE ERROR               E COMPILE ERROR   E RECOVERABLE ERROR        define  ENV    dev            Custom error handling vars     define  DISPLAY ERRORS   TRUE       define  ERROR REPORTING   E ALL   E STRICT       define  LOG ERRORS   TRUE        register shutdown function  shut         set error handler  handler            Function to catch no user error handler function errors        function shut              error   error get last             if  error  amp  amp    error  type    amp  E FATAL                handler  error  type     error  message     error  file     error  line                           function handler   errno   errstr   errfile   errline              switch   errno                case E ERROR     1                     typestr    E ERROR   break              case E WARNING     2                     typestr    E WARNING   break              case E PARSE     4                     typestr    E PARSE   break              case E NOTICE     8                     typestr    E NOTICE   break              case E CORE ERROR     16                     typestr    E CORE ERROR   break              case E CORE WARNING     32                     typestr    E CORE WARNING   break              case E COMPILE ERROR     64                     typestr    E COMPILE ERROR   break              case E CORE WARNING     128                     typestr    E COMPILE WARNING   break              case E USER ERROR     256                     typestr    E USER ERROR   break              case E USER WARNING     512                     typestr    E USER WARNING   break              case E USER NOTICE     1024                     typestr    E USER NOTICE   break              case E STRICT     2048                     typestr    E STRICT   break              case E RECOVERABLE ERROR     4096                     typestr    E RECOVERABLE ERROR   break              case E DEPRECATED     8192                     typestr    E DEPRECATED   break              case E USER DEPRECATED     16384                     typestr    E USER DEPRECATED   break                      message                 lt b gt      typestr                   lt  b gt      errstr                 in  lt b gt      errfile                 lt  b gt  on line  lt b gt      errline                 lt  b gt  lt br  gt             if   errno  amp  E FATAL   amp  amp  ENV      production                 header  Location  500 html                header  Status  500 Internal Server Error                        if    errno  amp  ERROR REPORTING               return           if DISPLAY ERRORS              printf   s    message              Logging error on php file error log            if LOG ERRORS              error log strip tags  message   0              ob start          include  content php        ob end flush      gt

User · Answer

Well  it seems possible to catch fatal errors some other way     ob start  fatal error handler     function fatal error handler  buffer        error   error get last        if  error  type      1              Type  message  file  line          newBuffer   lt html gt  lt header gt  lt title gt Fatal Error  lt  title gt  lt  header gt                         lt style gt                       error content                          background  ghostwhite                          vertical-align  middle                          margin 0 auto                          padding  10px                          width  50                                                error content label color  red font-family  Georgia font-size  16pt font-style  italic                         error content ul li  background  none repeat scroll 0 0 FloralWhite                                  border  1px solid AliceBlue                                  display  block                                  font-family  monospace                                  padding  2                                   text-align  left                                                 lt  style gt                         lt body style  text-align  center   gt                           lt div class  error content  gt                                lt label  gt Fatal Error  lt  label gt                                lt ul gt                                  lt li gt  lt b gt Line lt  b gt       error  line       lt  li gt                                  lt li gt  lt b gt Message lt  b gt       error  message       lt  li gt                                  lt li gt  lt b gt File lt  b gt       error  file       lt  li gt                                lt  ul gt                                 lt a href  javascript history back    gt  Back  lt  a gt                           lt  div gt                         lt  body gt  lt  html gt             return  newBuffer            return  buffer

User · Answer

You can t catch handle fatal errors  but you can log report them  For quick debugging I modified one answer to this simple code  function   fatalHandler          error   error get last            Check if it s a core fatal error  otherwise it s a normal shutdown     if   error     NULL  amp  amp  in array  error  type            array E ERROR  E PARSE  E CORE ERROR  E CORE WARNING                E COMPILE ERROR  E COMPILE WARNING E RECOVERABLE ERROR               echo   lt pre gt fatal error  n           print r  error           echo   lt  pre gt            die           register shutdown function    fatalHandler

User · Answer

Here is just a nice trick to get the current error handler method      lt  php     register shutdown function    fatalHandler         function   fatalHandler                  error   error get last                Check if it s a core fatal error  Otherwise  it s a normal shutdown         if  error     NULL  amp  amp   error  type       E ERROR                    It is a bit hackish  but the set exception handler                will return the old handler             function fakeHandler                     handler   set exception handler  fakeHandler                restore exception handler                if  handler     null                    call user func                       handler                      new ErrorException                           error  message                             error  type                            0                           error  file                             error  line                                exit                    gt    Also I want to note that if you call   lt  php     ini set  display errors   false     gt    PHP stops displaying the error  Otherwise  the error text will be send to the client prior to your error handler

User · Answer

Not really  Fatal errors are called that  because they are fatal  You can t recover from them

User · Answer

If you are using PHP    5 1 0 Just do something like this with the ErrorException class    lt  php        Define an error handler     function exception error handler  errno   errstr   errfile   errline             throw new ErrorException  errstr   errno  0   errfile   errline                 Set your error handler     set error handler  exception error handler            Trigger exception        try                  Try to do something like finding the end of the internet           catch ErrorException  e                   Anything you want to do with  e         gt

[php] How do I catch a PHP fatal (`E_ERROR`) error?

Examples related to php

Examples related to fatal-error