22

Is it possible to log stacktraces for php warnings? Or catch a warning and error_log() it?

There's some code causing warnings in my error log, but it's impossible to know what's causing these warnings without knowing the stack trace.

quano
  • 18,812
  • 25
  • 97
  • 108

4 Answers4

16

Just throw this at the start of your script:

set_error_handler(function($severity, $message, $file, $line) {
    if (error_reporting() & $severity) {
        throw new ErrorException($message, 0, $severity, $file, $line);
    }
});

Remove the if you want to log everything, even if it's suppressed.

mpen
  • 272,448
  • 266
  • 850
  • 1,236
15

There is an example of using set_error_handler() in conjunction with ErrorException to do just this:

https://php.net/manual/en/class.errorexception.php

You would just need to implement your custom logging functionality inside of the handler function.


UPDATE:

Note, this also works for warnings, and many other error types. For full compatibility, see the manual for set_error_handler():

https://php.net/set_error_handler

faintsignal
  • 1,828
  • 3
  • 22
  • 30
AJ.
  • 27,586
  • 18
  • 84
  • 94
2

Here you go:

class WarningWithStacktrace extends ErrorException {}
set_error_handler(function($severity, $message, $file, $line) {
    if ((error_reporting() & $severity)) {
        if ($severity & (E_WARNING | E_NOTICE | E_USER_WARNING | E_USER_NOTICE)) {
            $ex = new WarningWithStacktrace($message, 0, $severity, $file, $line);
            echo "\n" . $ex . "\n\n";
            return true;
        } else {
            throw new ErrorException($message, 0, $severity, $file, $line);
        }
    }
});

Errors/exceptions are thrown as usual, notices/warnings are printed only.

PS: Strict and other warning levels are not addressed, modify the code if needed...

mvorisek
  • 3,290
  • 2
  • 18
  • 53
2

I believe xdebug would go to log if that's how you have it enabled in your php.ini file, but it has stack tracing (with some bonus features like showing the local variables). It is not recommend for a production environment though.

XDebug Stack Traces

Paul DelRe
  • 4,003
  • 1
  • 24
  • 26
  • Agree it should not be enabled long-term in a production environment, as it will slow down the server. But it is easier to enable than adding an error handler to your bootstrap initialization (which may be buggy in itself - why reinvent the wheel?), and will also diagnose errors arising from hackers accessing your PHP files directly. If you don't have a common bootstrap, or it's not used in all cases, it also much more convenient to catch all possible errors this way. Enable it for a day or two, then look at the logs to see if there are any genuine errors. – Jake Dec 01 '22 at 01:09