On Tue, April 24, 2007 3:22 pm, Derick Rethans wrote: > On Tue, 24 Apr 2007, Pawe? Stradomski wrote: > >> Derick Rethans wrote: >> > On Tue, 24 Apr 2007, David Lindstrom wrote: >> > > Still, PHP should never segfault? >> > >> > Almost never... stack overflows are "okay". >> > >> >> I' ve run into PHP segfaulting (infinte loop of two constructors) >> recently and >> I think it should not happen in any case - no matter if the PHP >> script >> running is buggy or not. I makes debugging difficult and brings >> unpredicatble >> results. > > For debugging you install a debugger... which correctly warns you when > this happens. See: > http://xdebug.org/docs-settings.php#max_nesting_level
While this is certainly good advice, it seems to me that expecting every QA process to get complete code coverage and detect every possible combination of inputs that might overflow stack is just not realistic... Or am I missing something here? -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
