diff options
| author | Anatol Belski <ab@php.net> | 2017-07-11 16:34:45 +0200 |
|---|---|---|
| committer | Anatol Belski <ab@php.net> | 2017-07-11 17:01:59 +0200 |
| commit | 8a287c0ea0c437c32f30bfc6a411b967c4b8aafb (patch) | |
| tree | b02221447e7ffcd5df69e87751b24a8ce40c9a60 /ext/pcre/php_pcre.c | |
| parent | 9bcd93201f1679646011040093752a48992c0c6b (diff) | |
| download | php-git-8a287c0ea0c437c32f30bfc6a411b967c4b8aafb.tar.gz | |
Upgrade bundled PCRE to 8.41
HEADSUP! With PCRE 8.39 the JIT related code was changed in the way,
that additional valgrind options became almost unavoidable. Valgrind
had it already sometimes hard with JIT, now there are seem to be more
cases requiring special valgrind options.
For this reason, the new configure option --with-pcre-valgrind was
introduced. The option is development/debugging only and turns on the
Valgrind related pieces in PCRE, so then false positives are avoided
to the big part. In addition, run-tests.php was added a new valgrind
option, when the leak check is enabled and the test filepath contains
pcre.
Thus, to debug the code related to PCRE with JIT enabled, two things
would likely make sense
- configure --with-pcre-valgrind
- valgrind option --smc-check=all if run-tests.php is not used
The checks so far reveal no new issues.
Diffstat (limited to 'ext/pcre/php_pcre.c')
| -rw-r--r-- | ext/pcre/php_pcre.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/ext/pcre/php_pcre.c b/ext/pcre/php_pcre.c index 9779afaa36..750e720d74 100644 --- a/ext/pcre/php_pcre.c +++ b/ext/pcre/php_pcre.c @@ -175,6 +175,10 @@ static PHP_MINFO_FUNCTION(pcre) php_info_print_table_row(2, "PCRE JIT Support", "not compiled in" ); #endif +#ifdef HAVE_PCRE_VALGRIND_SUPPORT + php_info_print_table_row(2, "PCRE Valgrind Support", "enabled" ); +#endif + php_info_print_table_end(); DISPLAY_INI_ENTRIES(); |