#14136 [Opn->Csd]: Segfaults when forget xslt_free()

From: Date: Tue, 24 Sep 2002 08:27:56 +0000
Subject: #14136 [Opn->Csd]: Segfaults when forget xslt_free()
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-20172@lists.php.net to get a copy of this message
ID: 14136 Updated by: derick@php.net Reported By: lenar@vision.ee -Status: Open +Status: Closed Bug Type: Scripting Engine problem Operating System: Debian/Linux PHP Version: 4.0CVS-2001-11-2 Assigned To: sterling New Comment: great, let's close this one then Previous Comments: ------------------------------------------------------------------------ [2002-09-24 03:25:10] lenar@vision.ee I can't reproduce this myself too with PHP4.2.2. So it must have got fixed. ------------------------------------------------------------------------ [2002-09-23 17:38:07] jmoore@php.net I cant reproduce this on windows nor can rei (Ilia) on slackware. This bug is not really critical as it has a workaround of using xslt_free. Can you please provide us with a SHORT test script (Including the XSLT and XML required) which reproduces this behaviour so we can localize and fix this bug if it does exist. Status => User feedback. Many thanks, - James -- James Moore jmoore@php.net ------------------------------------------------------------------------ [2002-03-26 03:31:24] derick@php.net Sterling, can you please check this? Derick ------------------------------------------------------------------------ [2002-02-27 07:40:26] derick@php.net Assinging this to you sterling, have fun with it! ------------------------------------------------------------------------ [2001-11-20 15:21:51] zeev@php.net Doesn't look like a Zend problem to me. Apparently the table ends up containing the wrong entries (i.e., the same entry more than once) or, if the analysis is accurate, then the dependencies aren't properly implemented, and a resource (the parser) is freed prematurely. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14136 -- Edit this bug report at http://bugs.php.net/?id=14136&edit=1

« previous php.bugs (#20172) next »