PHP 4.0 Bug #8036 Updated: php_sablot.dll crashed php.exe

From: Date: Sat, 17 Feb 2001 22:27:33 +0000
Subject: PHP 4.0 Bug #8036 Updated: php_sablot.dll crashed php.exe
Groups: php.dev 
Request: Send a blank email to php-dev+get-46804@lists.php.net to get a copy of this message
ID: 8036 Updated by: sbergmann Reported By: sbergmann@php.net Old-Status: Analyzed Status: Closed Bug Type: Reproduceable crash Assigned To: sterling Comments: spoO, this was fixed by Sterling a while ago. Previous Comments: --------------------------------------------------------------------------- [2000-12-03 14:20:22] sterling@php.net Try the latest CVS and let me know if the problem still persists. --------------------------------------------------------------------------- [2000-12-02 06:35:39] sbergmann@php.net The latest CVS makes php.exe crash on startup, again. --------------------------------------------------------------------------- [2000-12-02 05:31:23] sterling@php.net Please try the latest cvs and let me know if this happens, thanks. --------------------------------------------------------------------------- [2000-11-30 08:52:48] sbergmann@php.net There is a problem in PHP_MSHUTDOWN_FUNCTION. The following comments make the crash go away, but I think the sablot extension will now leak memory: PHP_MSHUTDOWN_FUNCTION(sablot) { SABLOTLS_FETCH(); /* if (SABLOTG(processor)) { SablotUnregHandler(SABLOTG(processor), HLR_MESSAGE, NULL, NULL); SablotDestroyProcessor(SABLOTG(processor)); } */ return SUCCESS; } --------------------------------------------------------------------------- [2000-11-29 16:35:03] sbergmann@php.net After enabling php_sablot.dll (built, together with cgi/php.exe from latest CVS) PHP crashes on startup. The request is processed and the requested document is sent out. The Sablot extension is shown as loaded in phpinfo() but I haven't tested the exetension's functions. --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=8036&edit=2

« previous php.dev (#46804) next »