|
|
Posted by Jerry Stuckle on 08/19/06 12:58
Richard Levasseur wrote:
> Andy Hassall wrote:
>
>>On 18 Aug 2006 15:08:33 -0700, "lawrence k" <lkrubner@geocities.com> wrote:
>>
>> Re: the subject line:
>>
>> http://www.google.co.uk/search?q=segmentation+fault
>>
>> This first hit is informative.
>>
>>
>>>We made some changes to our server yesterday,
>>
>> What changes did you make?
>>
>>
>>>and ever since, every
>>>single installation of WordPress that was on the server has stopped
>>>running. Other PHP scripts still run fine, but WordPress is dead.
>>
>> OK, so you should reverse the changes you made.
>>
>> And, this should serve as a lesson to make changes to a test server first,
>>assuming this is a server where the application is worth some amount of money
>>greater than zero.
>>
>>
>>>I logged into the server using ssh and looked the Apache error_log. The
>>>only thing there was a whole bunch of lines like this:
>>>
>>>[Fri Aug 18 18:00:25 2006] [notice] child pid 27827 exit signal
>>>Segmentation fault (11)
>>>
>>>I'm not finding any PHP errors that might tell me what is wrong with
>>>WordPress.
>>>
>>>Can anyone give me advice about what to do?
>>
>> PHP should never suffer a segmentation fault; if it does, then there is
>>either:
>>
>> (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.
>
I've also had bad PHP code cause segfaults. It shouldn't happen, but
the interpreter isn't perfect.
Never had good PHP code cause a segfault, so that's good enough for me :-).
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|