ID: 40909
User updated by: adrynet at tiscali dot it
Reported By: adrynet at tiscali dot it
Status: Bogus
Bug Type: *Regular Expressions
Operating System: Linux Fedora / Redhat / CentOS
PHP Version: 4.4.6
New Comment:
> Yes, PHP 4.4.6 (as well as PHP 5.2.2) has PCRE 7.0 bundled.
So if is PCRE 7.0 the root cause we have to expect a Segmentation Fault
even in the next PHP 5.x update :| ?
thanks
Adriano C.
Previous Comments:
------------------------------------------------------------------------
[2007-03-26 11:18:18] [EMAIL PROTECTED]
Yes, PHP 4.4.6 (as well as PHP 5.2.2) has PCRE 7.0 bundled.
------------------------------------------------------------------------
[2007-03-26 11:06:54] adrynet at tiscali dot it
>You're asking wrong person, I can't answer your question since I'm
not
the author of PCRE.
Thanks for reply Tony. Do you know if 4.4.6 uses a new release of PCRE
and so we have this behaviour?
Have a nice day
Adriano C.
------------------------------------------------------------------------
[2007-03-26 10:59:43] [EMAIL PROTECTED]
>So why in this release PCRE should have "more appetite" on the same
usage
You're asking wrong person, I can't answer your question since I'm not
the author of PCRE.
------------------------------------------------------------------------
[2007-03-26 10:48:41] adrynet at tiscali dot it
Hi Tony,
It's strange because with PHP 4.4.6 we got Segmentation Fault using
preg_match_all() on with same regex pattern on the same source text that
both in previous versions of PHP 4.4.x and 5.x works perfectly.
So why in this release PCRE should have "more appetite" on the same
usage?
Have a nice day
Adriano C.
------------------------------------------------------------------------
[2007-03-26 10:07:35] [EMAIL PROTECTED]
Yet another PCRE stack overflow.
We got new INI options in PHP5 in order to "limit" the appetite of
PCRE, though they do not really fix the problem in PCRE library, which
is known to overflow the stack on certain expressions and there are no
plans on adding these options to PHP4.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/40909
--
Edit this bug report at http://bugs.php.net/?id=40909&edit=1
