--- Original Message -
From: "Jared Williams" <[EMAIL PROTECTED]>
To: "'Michael Vergoz'" <[EMAIL PROTECTED]>; "'Wez Furlong'"
<[EMAIL PROTECTED]>; "'Ilia Alshanetsky'" <[EMAIL PROTECTED]>
Cc: "'
> The problem is that setrlimit() need privilege to expand the
> process stack.
> I don't think it's a good idea to use this system call to fix
> the too-high-function-stack bug.
> There is no really way to fix correctly this bug.
> However I think we should re-examined the execution flow of
>
ow of PECL functions.
It is not normal PECL can eat all the stack.
-michael
- Original Message -
From: "Wez Furlong" <[EMAIL PROTECTED]>
To: "Ilia Alshanetsky" <[EMAIL PROTECTED]>
Cc: "Nuno Lopes" <[EMAIL PROTECTED]>; "PHPdev"
Sent
If we do do this, please make it optional; it's bad form when a module
or a library unilaterally changes a process-wide option or setting and
impacts a system that has already been tuned; the sysadmin may already
have set up appropriate limits.
--Wez.
On 2/21/06, Ilia Alshanetsky <[EMAIL PROTECTE
Nuno Lopes wrote:
In the last days I've exchanged some e-mails with PCRE's author because
of one more bug that appeared in our database about segfaults in PCRE
(related to stack overflows).
PCRE can consume a lot of stack, because of backtracking (thus
segfaulting PHP). Yesterday I've discovere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[response is at the bottom]
Ilia Alshanetsky wrote:
> Nuno Lopes wrote:
>> In the last days I've exchanged some e-mails with PCRE's author
>> because of one more bug that appeared in our database about segfaults
>> in PCRE (related to stack overf
Nuno Lopes wrote:
Hi,
In the last days I've exchanged some e-mails with PCRE's author because
of one more bug that appeared in our database about segfaults in PCRE
(related to stack overflows).
PCRE can consume a lot of stack, because of backtracking (thus
segfaulting PHP). Yesterday I've dis
Nuno Lopes wrote:
In the last days I've exchanged some e-mails with PCRE's author because
of one more bug that appeared in our database about segfaults in PCRE
(related to stack overflows).
PCRE can consume a lot of stack, because of backtracking (thus
segfaulting PHP). Yesterday I've discovere
Hi,
In the last days I've exchanged some e-mails with PCRE's author because of
one more bug that appeared in our database about segfaults in PCRE (related
to stack overflows).
PCRE can consume a lot of stack, because of backtracking (thus segfaulting
PHP). Yesterday I've discovered that when u
