Re: Current HEAD segfaults with Horde/CHORA

From: Date: Tue, 11 Feb 2003 22:57:26 +0000
Subject: Re: Current HEAD segfaults with Horde/CHORA
References: 1 2 3 4 5  Groups: php.dev 
Request: Send a blank email to php-dev+get-94178@lists.php.net to get a copy of this message
On Tue, Feb 11, 2003 at 03:17:53PM -0500, Derick Rethans wrote: | > David Brown wrote: | > | > I assume the crash on infinite recursion is a stack-overflow type thing, | > but is there any reason that doesn't trigger the 'Allowed memory | > exhausted' and exit cleanly? | > | >Just curious... :) | efficiency :) Adding checks for this will be 1) inaccurate, 2) slow and | thats enough not to do them :) Hi Derick: Sorry about leaving php-dev off of the Cc - your reply didn't make it back to the php-dev list, though you did indeed respond. :) A couple of followup questions: 1. The crashes I'm able to catch with <?php function a(){a();}a(); ?> stop GDB at zend_execute line 1489: zend_ptr_stack_n_push(&EG(arg_types_stack), 2, EX(fbc), EX(object).ptr); However, zend_ptr_stack_n_push seems to handle growth of the stack, and there aren't pointer dereferences anywhere else. Am I looking at the wrong section of code? The wrong stack, maybe? :) 2. Is the PHP stack size configurable, either at run-time or at compile-time? (That is, assuming it's defined by PHP and not a resource limitation/setting in the OS). Thanks in advance, - Dave dave@codewhore.org

« previous php.dev (#94178) next »