ID: 40624
Comment by: tom dot myny at tigron dot be
Reported By: test_junk at hotmail dot it
Status: No Feedback
Bug Type: PCRE related
Operating System: linux 2.4 i386
PHP Version: 4.4.5
New Comment:
Hello,
I have the same problem with PHP 4.4.7
[Thread debugging using libthread_db enabled]
[New Thread -1218357568 (LWP 2423)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1218357568 (LWP 2423)]
match (
eptr=0x89ea7f8 "Ingrediënten<p> een kloeke braadkip, ca. 2 Kg, bv.
eentje uit de Landes<p> 4 sjalotten<p> 100 g chocolade, extra donkere
bv. Cote (...)", ecode=0x897ed4a "Y", offset_top=4, md=0xbfdc2a10,
ims=0, eptrb=0x0,
flags=0, rdepth=5704)
at /usr/src/php-4.4.7/ext/pcre/pcrelib/pcre_exec.c:517
517 prop_value = 0;
(gdb) quit
This wasn't with 4.4.4 but i have also updated my distribution to the
latest debian stable version (etch)
Previous Comments:
------------------------------------------------------------------------
[2007-04-04 20:44:44] ted_johnson2 at yahoo dot com
Using the latest versions of apache2.2 and php (both installed via the
debian etch repository; also trying the CVS snapshot of php for
4/4/2007) this is still an issue.
Furthermore, the php.ini directives do nothing. I can set them to 1,
10, 100, or any value I choose and not see a positive change in the test
case. The failure is still 100% reproducible.
------------------------------------------------------------------------
[2007-03-08 01:00:01] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2007-02-28 11:49:42] test_junk at hotmail dot it
I downgraded the PCRE lib to the 6.6 release, the one shipped with php
4.4.4 and the problem appears to be resolved.
It's indeed a PCRE issue, I hope they will fix it in the future
releases.
------------------------------------------------------------------------
[2007-02-28 08:01:11] [EMAIL PROTECTED]
>Is this issue going to be fixed in the next release?
We got a workaround for it in PHP5, but we're not going to add it to
PHP4, so you have to upgrade your PHP first.
This issue (if it's really what it seems to be) is actually not PHP
problem, but a well-known PCRE issue.
Though, I wouldn't be 100% sure without a test-case.
------------------------------------------------------------------------
[2007-02-28 07:07:52] test_junk at hotmail dot it
Is this issue going to be fixed in the next release? Unfortunately it
breaks lots of things, including very popular apps. I will try to do my
best in finding the responsible php code but I'm not sure it will be
possibile.
Thanks for your interest in this matter.
------------------------------------------------------------------------
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/40624
--
Edit this bug report at http://bugs.php.net/?id=40624&edit=1
