#50519 [Com]: segfault in garbage collection when using set_error_handler and DomDocument

ID: 50519 Comment by: allan dot schmidt at xomit dot com Reported By: robin dot kunde at gmail dot com Status: Assigned Bug Type: Reproducible crash Operating System: * PHP Version: 5.3, 6 Assigned To: dmitry New Comment: Hi, let me just add, that at my production system, nothing in regard to XML works right now. Creating an instance of DOMDocument or simpleXML simply crashes the setup. I am using Windows IIS 7 with fastCGI and have tried with both PHP 5.2.11 and 5.3.1. The result is the same. Until now I had it running on another Windows server, but using Apache, without any problems. Is there a fix on it's way? It's way? Previous Comments: ------------------------------------------------------------------------ [2009-12-31 18:21:00] jani@php.net Well, you fixed it only with --enable-debug being used? :) ------------------------------------------------------------------------ [2009-12-31 18:17:02] jani@php.net Dmitry, I don't know what you fixed but the example script still causes a segfault, with same backtrace I posted before.. ------------------------------------------------------------------------ [2009-12-25 13:11:45] dmitry@php.net This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2009-12-25 13:11:19] svn@php.net Automatic comment from SVN on behalf of dmitry Revision: http://svn.php.net/viewvc/?view=revision&revision=292624 Log: Fixed bug #50519 (segfault in garbage collection when using set_error_handler and DomDocument) ------------------------------------------------------------------------ [2009-12-18 18:47:43] jani@php.net Quite likely same as bug #50382 ------------------------------------------------------------------------ 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/50519 -- Edit this bug report at http://bugs.php.net/?id=50519&edit=1