[wp-hackers] wp-hackers Digest, Vol 74, Issue 90

[Otto]

On Fri, Mar 25, 2011 at 9:02 AM, John Eckman <eckman.john at gmail.com> wrote:
> Maybe bad choice of words - you do get a segmentation fault and the child
> ids of Apache processes are killed, but true, Apache itself stays up.
>
> It's highly repeatable and reproducable - but in the context of WPBook
> 2.1.4 and WordPress 3.0.5. With no additional themes other than the
> default installed, and no additional plugins other than WPBook.
>
> Certainly could be the way WPBook is both filtering theme_root and calling
> get_themes in the same context.
>
> I'll keep investigating- likely it is a problem in our code.

PHP code should never be able to cause a segfault, as it's an
interpreted language.

So if you're actually segfaulting, then you've found a bug in the
version of PHP or Apache you're using, or there's a library
incompatibility, or something like that.

-Otto