Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33075
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.55.154.25 as permitted sender)
Message-ID: <003701c82386$ce65ff80$4101a8c0@pc07653>
To: "Matthias Pigulla" <mp@webfactory.de>,
	<internals@lists.php.net>
References: <00A2E2156BEE8446A81C8881AE117F199A02FC@companyweb>
Date: Sat, 10 Nov 2007 10:45:27 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] preg_match and shared libpcre3 bug
From: nlopess@php.net ("Nuno Lopes")

> With installing a security update for the pcre3 library on Debian
> (http://lists.debian.org/debian-security-announce/debian-security-announ
> ce-2007/msg00177.html), preg_match('|^\(|', 'xxx') suddenly returns 1
> instead of 0 using PHP 5.1.6.

the correct value is 0, yes.


> The thing is - I have built PHP using the bundled PCRE library and the
> error happens only with the apache2 module, not with a CLI binary.
> phpinfo() shows PCRE 6.6 and ldd shows no dependencies against the
> shared libpcre.so.3, neither for the php-cli binary nor for the apache
> module.
>
> Any ideas what might cause that? I can't see why the shared library
> update makes a difference at all.

You are right that updating the shared library shouldn't matter. If the 
problem happens only with apache2 it suggests that there is some symbol 
clashing problem. Please try with a recent PHP version and report if it 
doesn't work (I remember fixing a bunch of these lately).
Anyway I would advise you to upgrade PHP to a more recent version, as PCRE 
6.6 has some security problems.


Nuno