Bug #14783 Updated: Using unlink causes segfault

ID: 14783 Updated by: mfischer Reported By: mfkahn2@yahoo.com Old Status: Closed Status: Feedback Bug Type: DOM XML related Operating System: RH6.2/Apache/libxml2.4.12 PHP Version: CVS Jan. 1 2002 New Comment: Did the same before I replied and it didn't crash, hm. What were your ./configure options? Do you have another small, self-contained sample? Feedback. Previous Comments: ------------------------------------------------------------------------ [2002-01-01 11:15:45] mfkahn2@yahoo.com Just checked out and built from CVS this morning (2002/1/1). The test script still crashes. ------------------------------------------------------------------------ [2002-01-01 07:11:54] mfischer@php.net This has been fixed in CVS. ------------------------------------------------------------------------ [2001-12-31 16:16:27] mfkahn2@yahoo.com Symptoms: - using unlink() causes segfault Script to reproduce: <?php $xml = <<<END_XML <?xml version="1.0"?> <test> <foo id="x">Hello</foo> <foo id="y">World</foo> </test> END_XML; $dom = xmldoc($xml); // this so I can see it. header('Content-type: text/plain'); $ctx = $dom->xpath_new_context(); $res = xpath_eval($ctx,"//foo"); foreach ($res->nodeset as $child) { $child->unlink(); } echo $dom->dumpmem(); ?> Other notes: - some cursory debugging I did suggested that it was the cleanup routines at the end of the script that were causing the crash. Looking at php_domxml.c, the recursive node memory cleanup appears to be choking on a pointer already freed during the unlink() call. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=14783&edit=1