Bug #16360 Updated: Segmentation fault in Array functions

ID: 16360 Updated by: wolfram@schlich.org Reported By: nohn@php.net Status: Analyzed Bug Type: Scripting Engine problem Operating System: Linux, Windows PHP Version: 4.0CVS-2002-03-3 New Comment: Ok, ZendOptimizer disabled, patch works as expected. Any patch like the one Joerg suggested in sight? Previous Comments: ------------------------------------------------------------------------ [2002-04-01 01:32:52] yohgaki@php.net When you report error. Disable Zend Optimizer _ALWAYS_. We don't support ZendOptimizer and it's waste of time for both of us. Zend optimizer probably does not work with the patch. To locate line, use die(). ------------------------------------------------------------------------ [2002-03-31 21:44:32] wolfram@schlich.org Please give me a hint how to locate the line, for I don't know :-) I'm using the Zend Optimizer in addition, nothing else. ------------------------------------------------------------------------ [2002-03-31 20:56:36] yohgaki@php.net wolfram, Could you locate which line is causing following error? "Unsupported operand types in Unknown on line 0" I don't get this error message with my applicatins. Are you using any cache products? ------------------------------------------------------------------------ [2002-03-31 12:42:45] wolfram@schlich.org After applying the patch above, my Apache segfaults on scripts which ran fine before or just prints "Unsupported operand types in Unknown on line 0". Using PHP 4.2.0RC1. ------------------------------------------------------------------------ [2002-03-31 12:21:32] joerg@infolinux.de Increasing the refcount width from short to long doesn't solve the issue. A strict upper limit test is badly needed to check whether the refcounter can be increased in the given limit or not. I suggest to throw a memory exhausted error with a hint that no more reference counters could be allocated. ------------------------------------------------------------------------ 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/16360 -- Edit this bug report at http://bugs.php.net/?id=16360&edit=1