[pcre-dev] [Bug 1617] Segmentation fault in preg_match() wit…

Top Page
Delete this message
Author: Philip Hazel
Date:  
To: pcre-dev
Subject: [pcre-dev] [Bug 1617] Segmentation fault in preg_match() with PHP 5.6.8/5.5.24
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1617




--- Comment #1 from Philip Hazel <ph10@???> 2015-04-18 16:34:56 ---
Because you have used PCRE via PHP, you do not say which version of PCRE you
are using. I have tried your pattern using the current release, and there is no
problem. It just gives an error message:

$ valgrind pcretest zzz
==23719== Memcheck, a memory error detector
==23719== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==23719== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==23719== Command: pcretest zzz
==23719==
PCRE version 8.36 2014-09-26

/((?1)+()(())())*())/
Failed: recursive call could loop indefinitely at offset 4
==23719== 
==23719== HEAP SUMMARY:
==23719==     in use at exit: 0 bytes in 0 blocks
==23719==   total heap usage: 5 allocs, 5 frees, 100,861 bytes allocated
==23719== 
==23719== All heap blocks were freed -- no leaks are possible
==23719== 
==23719== For counts of detected and suppressed errors, rerun with: -v
==23719== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)


ChangeLog item 20 for the 8.36 release looks as though it might have fixed a
bug that is relevant here. Please check which release of PCRE is being used by
PHP.


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email