You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems whoops is focusing more on exception handling than error handling. I am currently using Xdebug and the HTML stacktraces. http://xdebug.org/docs/stack_trace I'm wondering if the whoops error handler could be improved by integrating with Xdebug.
Whoops doesn't show me the line number where the error occurred or a stacktrace. If I use xdebug's error messages I do get line numbers and a stacktrace.
Edit: After looking into it, you can get the backtrace without using Xdebug. I made some progress by adding this code to getFrames() in Inspector.php
if ($this->exceptioninstanceof ErrorException) {
$frames = debug_backtrace();
}
The text was updated successfully, but these errors were encountered:
An other option is to improve extensibility of Inspector by adding a protected setter for frames attribute so we're allowed to set our own frames from Xdebug.
+1 some frameworks are error- rather than exception-centric (*cough* WordPress) and it would be very nice to have backtrace for errors (even native PHP one for starters, without xdebug extras).
update hm, I got first impression it's not showing backtraces for errors in general, but sometimes it does and sometimes it doesn't.
It seems whoops is focusing more on exception handling than error handling. I am currently using Xdebug and the HTML stacktraces. http://xdebug.org/docs/stack_trace I'm wondering if the whoops error handler could be improved by integrating with Xdebug.
For example, using this example code:
Whoops doesn't show me the line number where the error occurred or a stacktrace. If I use xdebug's error messages I do get line numbers and a stacktrace.
Edit: After looking into it, you can get the backtrace without using Xdebug. I made some progress by adding this code to getFrames() in Inspector.php
The text was updated successfully, but these errors were encountered: