Edit report at https://bugs.php.net/bug.php?id=62266&edit=1

 ID:                 62266
 Updated by:         cataphr...@php.net
 Reported by:        lance dot lovette at gmail dot com
 Summary:            Custom extension segfaults during xmlParseFile with
                     FPM SAPI
-Status:             Assigned
+Status:             Feedback
 Type:               Bug
 Package:            XML related
 Operating System:   CentOS release 6.2 (Final)
 PHP Version:        5.4Git-2012-06-08 (snap)
 Assigned To:        cataphract
 Block user comment: N
 Private report:     N

 New Comment:

Please try using this snapshot:

  http://snaps.php.net/php5.4-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/




Previous Comments:
------------------------------------------------------------------------
[2012-06-09 16:32:31] cataphr...@php.net

Automatic comment on behalf of cataphract
Revision: 
http://git.php.net/?p=php-src.git;a=commit;h=503358c1797e0f7b05fb49f22dd44bc7f517069f
Log: Fix bug #62266

------------------------------------------------------------------------
[2012-06-08 17:56:01] cataphr...@php.net

I'll take a look as this was very likely caused by a change I made.

------------------------------------------------------------------------
[2012-06-08 17:45:11] lance dot lovette at gmail dot com

Description:
------------
I have a custom extension that has been in use since 2001. When I upgraded to 
PHP 
5.4 it caused php-fpm to segfault. The extension uses xmlParseFile to load an 
XML 
configuration file in MINIT. The CLI build of PHP does NOT segfault and 
functions 
as expected.

Test script:
---------------
I created a trivial extension that calls xmlParseFile in MINIT:
https://gist.github.com/2896852

Expected result:
----------------
I expect xmlParseFile to succeed.

Actual result:
--------------
Output from configure, a gdb backtrace and a list of modules 
and phpinfo when the crashing extension is disabled:
https://gist.github.com/2896980


------------------------------------------------------------------------



-- 
Edit this bug report at https://bugs.php.net/bug.php?id=62266&edit=1

Reply via email to