Battling something rather interesting in 6.x pressflow, which has backported some of 7.x's error handling.
If the php library imap_open triggers a connection error, when drupal error handling, global variables aren't set ($user is empty) and debug_backtrace only contains one item, e.g. _drupal_error_handler, so once that is removed $backtrace[0] is not set and triggers another error.
I have no idea how to reproduce this condition outside of imap_open; trying to google the situation didn't help at all.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 6f1d010b1396e20102c616de5146a47e.png | 110.81 KB | hefox |
| drupal_error_handler_backtrace.6.do-not-test.patch | 912 bytes | hefox | |
| drupal_error_handler_backtrace.patch | 531 bytes | hefox |
Comments
Comment #3
hefox commentedScreenshot of when this error occurs, and issue of an example of this error in the wild
Comment #4
alx_benjamin commentedI believe this belongs to D6 branch not D8
Please re-assign if I am wrong.
Thank you
-------------------------------------------------
Sponsored by http://reallifedesign.co.uk/
Comment #5
David_Rothstein commentedLooks like a Drupal 8 patch to me (but needs a reroll). The issue summary mentions Drupal 6 Pressflow because that's where it was first encountered, but the idea is that it may be a bug in the error handling code that's also found in Drupal 7 and Drupal 8 core.
Comment #16
mstrelan commentedIs this still relevant? If so, please provide an issue summary update and steps to reproduce. The patch no longer applies, the function in question was moved in #2157691: Move some helper methods in errors.inc to an Error utility class, so would need a reroll.
Comment #18
quietone commentedThis began 9 years ago with Drupal 6 and there has been hardly any discussion. More information was asked for 6 months ago and none has been supplied. Even the Issue Summary states that there is no known way to reproduce the issue. It is time to close this one.