note 85564 deleted from function.debug-print-backtrace by tularis
| From: | tularis@php.net | Date: | Sat, 06 Sep 2008 17:21:46 +0000 |
| Subject: | note 85564 deleted from function.debug-print-backtrace by tularis | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-144195@lists.php.net to get a copy of this message | ||
Note Submitter: Rajeev Jha
Reason: bad code
----
You can use debug_print_backtrace in your error templates. This can be a good debugging aid. Inside
your error template
<?php
//clean out the script output
ob_end_clean();
//start buffering
ob_start();
$stackTrace = '' ;
if(intval(T_Config::getInstance()>get_stack_trace()) == 1 ) {
debug_print_backtrace();
//get output buffer contents
$stackTrace = ob_get_contents();
}
ob_end_clean();
//send raw error to our log file
$errorstr = $stackTrace;
error_log ("$file:$line : $errorstr \n",3,$logFile);
// translate the raw error for template
$bindings['ERROR_MESSAGE'] = some_encrypt_fn($errorstr) ;
//output error template
//start buffering again
ob_start();
?>
so when an error happens your site users will see some encrypted form of stack trace that can be
mailed back to you.