PHP 4.0 Bug #5927 Updated: Incorrect shutdown order of modules
| From: | sniper@php.net | Date: | Sat, 30 Dec 2000 16:48:13 +0000 |
| Subject: | PHP 4.0 Bug #5927 Updated: Incorrect shutdown order of modules | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-42727@lists.php.net to get a copy of this message | ||
ID: 5927
Updated by: sniper
Reported By: ddebene@messagingdirect.com
Old-Status: Feedback
Status: Closed
Bug Type: Dynamic loading
Assigned To:
Comments:
No feedback, considered fixed.
--Jani
Previous Comments:
---------------------------------------------------------------------------
[2000-11-27 05:34:22] sniper@php.net
Is this still happeningn with latest snapshot
from http://snaps.php.net/ ?
--Jani
---------------------------------------------------------------------------
[2000-08-02 17:39:10] ddebene@messagingdirect.com
This occurs with statically or dynamically linked modules, but I am only experiencing it myself with
dynamically linked extensions. I have configured PHP to load two extensions I have created at run
time, let's call them A and B. A relies on behaviour of B. I have ordered them in the php.ini
file so that A is before B, and thus A gets initialized before B (which is required for B to work
properly). However, on shutdown, A is also shutdown before B, and since B requires A to be still
running to shut down, there is a core dump.
Modules should be getting shut down in the reverse order that they are started, to preserve
dependencies.
I've actually patched this myself, here is the simple fix:
Zend/zend_hash.c
539c539
< p = ht->pListHead;
---
> p = ht->pListTail;
542c542
< p = p->pListNext;
---
> p = p->pListLast;
---------------------------------------------------------------------------
Full Bug description available at: http://bugs.php.net/?id=5927