Posted by Andy Hassall on 08/19/06 15:39

On 19 Aug 2006 04:36:42 -0700, "Richard Levasseur" <richardlev@gmail.com>
wrote:

>> (a) a bug in PHP
>> (b) a bug in a PHP extension
>> (c) a bug in a library loaded by PHP core
>> (d) a bug in a library loaded by a PHP extension
>> (e) something bizarrely wrong with your system as a whole
>
>(f) Seg faults can also occur if there is too much recursion, which can
>be caused by user PHP code.

That's arguably a case of (a); the out of memory / stack overflow condition
should be caught and gracefully raised as a fatal error message, not as
segfaulting the process.

Although looking at bugs.php.net there's various reports of this, with the PHP
maintainers marking them as "Won't Fix" or "Bogus".

And: http://news.php.net/article.php?group=php.internals&article=8851

Admittedly, if you've already filled the stack, then calling an error handling
function may be a challenge ;-)

--
Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool

• Next in forum: Re: XML communication suggestions
• Prev in forum: Re: HTMLPurifier - Standard Compliant HTML Filtering
• Thread view: Re: what is a segmentation fault, and why is it killing PHP on my server?

[Reply to this message]