On Feb 25, 2006, at 4:47 AM, Michael Vergoz wrote:
You see function what need a prevention ? contact me
[EMAIL PROTECTED]
Hello,
How about one that needs less prevention? Would this patch (or another
like it) allow for the elimination of the current recursion guard for
__get, etc?
ht
Nuno Lopes wrote:
Basicly your patch does just try to automatically detect the maximum
execution depth limit, that can be manually set with xdebug or
hardened-php patch for quite a while now...
which is not bad for the average user. I personally like the patch
(although it needs some tweaking
Basicly your patch does just try to automatically detect the maximum
execution depth limit, that can be manually set with xdebug or
hardened-php patch for quite a while now...
which is not bad for the average user. I personally like the patch (although
it needs some tweaking), but the idea is t
beside the fact that I think the correct way to stop the script is
zend_bailout() and not php_handle_aborted_connection()
and that your code will fail on systems where the stack is growing into
the opposite direction.
Stefan Esser
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
Basicly your patch does just try to automatically detect the maximum
execution depth limit, that can be manually set with xdebug or
hardened-php patch for quite a while now...
This kind of protection was rejected before to get into core and most
probably will be rejected again...
Stefan Esser
--
Hello,
ZDSP is a module to allow the Zend engine to know when it will go too much
far within the stack. In fact this module to allow to prevent a possible
segfault from the script.
If you type (php 5.1) :
php -r 'function foo() { foo(); } foo();'
You will get a segfault because foo() will go
