Manuel Lemos wrote:
Hello,
On 10/01/2004 11:20 AM, Olaf Van Der Spek wrote:
I was not aware that memory allocation failures could make PHP to
exit its process but since it seems intentional there must be a
reasoning behind that for which I am not the person that should
explain. Maybe the reason has to due to the fact that when memory
allocation fails, PHP allocation code can't be certain about memory
integrity.
But this does mean the policy does allow scripts to crash the
engine/server.
The way I see it, calling exit() is not a crash. If the code was
Indeed, I should've added "or fatal error".
But from the script's point of view, it's the same as a crash.
accessing invalid memory addresses that would cause it segmentation
faults, that would crash *ONE* process, you only see an entry in the
server error log, the child process would be restarted, but it still
would not crash the whole server as you seem to be thinking.
Yes, assuming you run on a non-threaded server.
But isn't the goal to get PHP4/5 safe for multi-threaded servers too?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
