Re: [patch] Zend/zend_objects_API.c - bug #29980 (segfault while executing __destruct())

From: Date: Fri, 10 Sep 2004 08:03:48 +0000
Subject: Re: [patch] Zend/zend_objects_API.c - bug #29980 (segfault while executing __destruct())
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-12705@lists.php.net to get a copy of this message
Well, if the engine is unstable state why the registered shutdown function is being executed then ? :) Andrey Andi Gutmans wrote:
I think this makes sense because PHP could be in an unstable state. Think EG(exit_status) covers all possible situations? No time to check now how it differs from CG(unclean_shutdown) which is most often used. Andi At 09:57 AM 9/10/2004 +0400, Antony Dovgal wrote:
And the last one, the most questionable patch. ATM ZE2 calls destructor at the end of the request and no matter is there were a fatal error (which should probably stop executing the script). In some cases it leads to nasty segfaults (me and report's author can reproduce it, but others can't. weird..). Some persons (hello, Andrey =)) think that this could be a useful feature, but for me it's just an inconsistency. IMO destructors should not be called after fatal errors, because they can cause even more harm. -- Wbr, Antony Dovgal aka tony2001 tony2001@phpclub.net || antony@dovgal.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.internals (#12705) next »