Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10884 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27129 invoked by uid 1010); 3 Jul 2004 08:27:55 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 27081 invoked from network); 3 Jul 2004 08:27:55 -0000 Received: from unknown (HELO mx.thebrainroom.net) (69.55.226.195) by pb1.pair.com with SMTP; 3 Jul 2004 08:27:55 -0000 Received: by mx.thebrainroom.net (Postfix, from userid 517) id 4682C14880CD; Sat, 3 Jul 2004 01:27:54 -0700 (PDT) Received: from BAUMBART (p508EB86C.dip.t-dialin.net [80.142.184.108]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx.thebrainroom.net (Postfix) with ESMTP id 046E014880CB; Sat, 3 Jul 2004 01:27:48 -0700 (PDT) Date: Sat, 3 Jul 2004 10:27:57 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <415710743.20040703102757@marcus-boerger.de> To: Andi Gutmans , Florian Schaper Cc: internals@lists.php.net In-Reply-To: <014e01c4607e$c40f0140$9d00a8c0@saiwala> References: <014e01c4607e$c40f0140$9d00a8c0@saiwala> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on jc.thebrainroom.net X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no version=2.63 X-Spam-Level: X-TBR-Filter: Virus scanned and defanged Subject: Re: [PHP-DEV] [PATCH] destructors called after module shutdown From: helly@php.net (Marcus Boerger) Hello Florian, hello Andi to me this is the way to go. At least the order of shutdown pieces is correct with this patch but maybe Andi has a better idea? regards marcus Friday, July 2, 2004, 11:51:44 PM, you wrote: > Currently object's destructors are called in the zend_deactivate function in > main.c after the modules > request_shutdown_func has been called (main.c - > php_call_shutdown_functions(void); ) . > Since no code should be executed after module request shutdown unexpected > behaviour might > occur like the one descibed in bug#27555 affecting the session extension.