Make WordPress Core

Opened 17 years ago

Closed 17 years ago

#6672 closed defect (bug) (invalid)

define('SAVEQUERIES', true) = debug_backtrace() = Error 500

Reported by: ozh's profile ozh Owned by:
Milestone: Priority: lowest
Severity: minor Version: 2.5
Component: General Keywords:
Focuses: Cc:

Description

This won't stop the earth rotation, but I've come across an annoying bug that I'm having difficulties to identify precisely.

Fact:
define('SAVEQUERIES', true); in my wp-config.php makes everything break with an Error 500.

Symptoms:
Error 500, log says "Premature end of script headers: /dh/cgi-system/php5.cgi" which means basically anything.

Culprit:
Function get_caller() in wp-db.php is the one causing the error. In that function, this particular line is to blame: $bt = debug_backtrace();
No clue why debug_backtrace() break things, though, and @debug_backtrace() doesnt help.

Server specs:
PHP 5.2.3, Apache running CGI/FastCGI, whole phpinfo()

This ticket is mostly for the record if anyone happens to search here for the same problem, even if it's going to get a wontfix/worksforme/cantreproduce. Cheers :)

Change History (5)

#1 @tellyworth
17 years ago

A bit of googling suggests Zend Optimizer might cause debug_backtrace() to trigger a 500 error on CGI servers. Can you test with that disabled?

#2 @ozh
17 years ago

I don't have access to php.ini so I guess I can't ...

#3 @ryan
17 years ago

  • Milestone changed from 2.5.2 to 2.9

Milestone 2.5.2 deleted

#4 @mrmist
17 years ago

Can't reproduce, with zend / php 5.2.5 / cgi

Not exactly the same config I grant, but it doesn't seem to "break everything".

#5 @jacobsantos
17 years ago

  • Keywords SAVEQUERIES debug_backtrace removed
  • Milestone 2.9 deleted
  • Resolution set to invalid
  • Status changed from new to closed

This belongs on the support forums until it is known what in WordPress is causing the problem if anything. Most likely a bug in PHP executable or something. Anything done in WordPress at the moment will only mask the real issue.

Note: See TracTickets for help on using tickets.