| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 1.10.16 |
| Bug #1630 | debug_backtrace - performance killer.. | ||
|---|---|---|---|
| Submitted: | 2004-06-14 00:48 UTC | ||
| From: | alan_k | Assigned: | cellog |
| Status: | Closed | Package: | PEAR |
| PHP Version: | 4.3.7 | OS: | all |
| Roadmaps: | (Not assigned) | ||
[2004-06-14 00:48 UTC] alan_k
Description:
------------
I think we should comment out debug_backtrace in PEAR_Error.. - it causes more problems than it solves..
If users need backtraces let them removed the comments.. - it's would be rare to require the backtrace on all the time.
Comments
[2004-06-18 07:39 UTC] smith at backendmedia dot com
Well removing it would be a BC booboo. So all we can do is make it optional.
[2004-10-22 05:46 UTC] cellog
This bug has been fixed in CVS.
In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pear.php.net.
In case this was a pear.php.net website problem, the change will show
up on the website in short time.
Thank you for the report, and for helping us make PEAR better.
I added a new static property to PEAR_Error
<?php
require_once 'PEAR.php';
$a = &PEAR::getStaticProperty('PEAR_Error', 'skiptrace');
$a = true;
?>
This code will disable all debug_backtrace() in PEAR_Error calls