In #1163356: New error handling option: Backtrace and normal message we've added the option of displaying both the backtrace and Drupal's standard message, mainly because the backtrace (using krumo()) sometimes wasn't showing.

I've just had this happen again in #1323938-9: Trying to get property of non-object in _mail_edit_load and had to walk the OP through replacing our krumo() call with a dpm() call in order to see the backtrace.

Right now we're offering the following options:

Devel Settings

I propose to turn this into a multi-selection box:

  • Standard Drupal
  • Krumo backtrace using dpm()
    (appears in the message area, as long as there's not too much data)
  • Krumo backtrace using krumo()
    (appears outside of the page but may be hidden, depending on the theme and where in the page construction process the error is generated)

This will allow us to select any combination as needed.

Also, the OP in the other thread asked whether there was a way to test if Krumo was actually working. It would be useful to have a "preview" link to simulate an error.

Any thoughts?

Files: 
CommentFileSizeAuthor
#2 devel_error_handlers.1326510.2.patch10.29 KBsalvis
PASSED: [[SimpleTest]]: [MySQL] 2 pass(es).
[ View ]
devel_backtrace_options.png2.65 KBsalvis

Comments

I'm the OP described above, and I'm all for the suggested changes. Our debugging session would have been much easier if we didn't have to spend a lot of time trying to deal with krumo backtraces that weren't showing up.

Status:Active» Needs review
StatusFileSize
new14.99 KB
new10.29 KB
PASSED: [[SimpleTest]]: [MySQL] 2 pass(es).
[ View ]

Here's a screenshot and a patch that applies to both D8 and D7.

(screenshot)

Status:Needs review» Fixed

No comments — committed to D8/D7.

Thanks, sah62.

No problem - thanks for listening!

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.