Hmm, this is an idea. (I don't know yet if it good or bad) Current problem occurs because the same debug_backtrace is called during exception creation. Probably we can disable storing of "object" in case of backtrace for exception. This should solve the problem.
Thanks. Dmitry. > -----Original Message----- > From: Sebastian Bergmann [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 01, 2005 10:09 AM > To: internals@lists.php.net > Subject: [PHP-DEV] Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / > zend_builtin_functions.cphp-src NEWS > > > Dmitry Stogov schrieb: > > Yes. But with Sebastian's patch object is stored in bactrace. So > > refcount is more then 1 and we cannot simple destroy it. > > Would it help to move the functionality I need from > debug_backtrace() into a new function or make it optional in > debug_backtrace()? > > -- > Sebastian Bergmann > http://www.sebastian-bergmann.de/ > GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 > C514 B85B 5D69 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
