RE: note 85177 rejected and deleted from function.debug-backtrace by notes editor felipe

Hello Felipe, Please read the comment posted by me carefully. It is not one of the following: - a question - a bug report - a feature request What it is: -A user contributed note. A pointer that might help someone who is using debug_backtrace and getting the "PHP has encountered an Access Violation at 7C8224B2". If they stop requesting backtraces in their error reports, the access violation error is likely to go away. -rchaube -----Original Message----- From: php-notes@lists.php.net [mailto:php-notes@lists.php.net] Sent: Tuesday, August 19, 2008 9:51 PM To: rchaube@staff.atlantic.net Subject: note 85177 rejected and deleted from function.debug-backtrace by notes editor felipe You are receiving this email because your note posted to the online PHP manual has been removed by one of the editors. Read the following paragraphs carefully, because they contain pointers to resources better suited for requesting support or reporting bugs, none of which are to be included in manual notes because there are mechanisms and groups in place to deal with those issues. The user contributed notes are not an appropriate place to ask questions, report bugs or suggest new features; please use the resources listed on <http://php.net/support> for those purposes. This was clearly stated in the page you used to submit your note, please carefully re-read those instructions before submitting future contributions. Bug submissions and feature requests should be entered at <http://bugs.php.net/>. For documentation errors use the bug system, and classify the bug as "Documentation problem". Support and ways to find answers to your questions can be found at <http://php.net/support>. Your note has been removed from the online manual. ----- Copy of your note below ----- I am not sure but *i think* that the use of debug_backtrace might be linked to the following error that many dread "PHP has encountered an Access Violation at 7C8224B2" I had to discontinue the use of this function to get detailed backtraces during error handling to get around the sporadic incidences of the above error. There certainly are other problems that seemed to have fixed the above, but i was unable find anything that conclusively fixes the error at the time of posting: http://www.vbulletin.com/forum/archive/index.php/t-211513.html Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.0/851 - Release Date: 6/16/2007 12:50 PM Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.0/851 - Release Date: 6/16/2007 12:50 PM