Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42454
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 83.243.58.133 cause and error)
To: Derick Rethans <derick@php.net>
Cc: dmitri@zend.com, PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <alpine.DEB.2.00.0901021655350.14003@kossu.ez.no>
References: <alpine.DEB.2.00.0901021655350.14003@kossu.ez.no>
Content-Type: text/plain
Date: Fri, 02 Jan 2009 23:23:18 +0100
Message-ID: <1230934998.6125.152.camel@goldfinger>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] call_user_func segfault
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2009-01-02 at 16:55 +0100, Derick Rethans wrote:
> Hello,
> 
> I've been running into a strange segfault with PHP 5.2.x (it works in 
> PHP 5.3) when using call_user_func() recursively. I can not find out 
> what causes it, but I did manage to have a simple test case. For the 
> test to crash, you either need a debug build of PHP, or valgrind + 
> USE_ZEND_ALLOC=0. You need run the script from within the "test" 
> directory as it assumes file system layout. 

I didn't test it as I have no 5.2 right now at hand on this box but I
think call_user_func messes with references in parameters to the called
function. In 5.3 this is fixed by zend_parse_parameters. I saw some code
(Serendipity's way of using Smarty) break with 5.3 since reference
handling changed there, didn't investigate but 5.3 seemed to be correct
on first sight.

Not sure if that's enough of an pointer to help debugging that issue...

johannes