Re: Considering segfaults: how to protect other requests?

From: Date: Sat, 21 Jan 2012 22:24:16 +0000
Subject: Re: Considering segfaults: how to protect other requests?
References: 1 2 3 4 5 6  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-9062@lists.php.net to get a copy of this message
On 21/01/12 22:25, Rasmus Lerdorf wrote:
He meant that you can have memory corruption without a segfault. So that one process can survive in a corrupted state and affect the next request to that process. Which is quite true, of course, but the scope of the original question was whether such memory corruption could jump from one process to another, and that is of course not possible. -Rasmus Yes. The original request looked a bit like "If I use preforked I don't have to
worry about writing correct code". I was pointing out that there could still be inter-request corruption even with preforked. Although rereading it now, it may equally have been on the line of how to make a variable static for the request instead (|in which case the answer would be about ZEND_BEGIN_MODULE_GLOBALS|). Or about something else completely different. It's an odd question which probably isn't querying what it wants.

« previous php.pecl.dev (#9062) next »