------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=861 --- Comment #1 from Philip Hazel <[email protected]> 2009-07-03 11:19:09 --- On Fri, 3 Jul 2009, David Gausmann wrote: > The code is the following: > $sContent = 'Call ABCDEFGHJIKLMNOPQRSTUVWXYZ("Lorem Ipsum dolor sit amet, > consectetuer elitr\'" & VARIABLE & "\'" & vbCRLF & > > vbCRLF & "Lorem > ipsum dolor sit amet conset" & vbCRLF & > > vbCRLF & "Lorem ipsum dolor > sit > amet consectetuer sadipscing.")'; > echo > preg_match('/^(?:[^"]|"(?:[^"]|"")*")*(?:var_alloc)\s*\(?\s*"[^"]+".*$/i', > $sContent); > > As you can see the string (which shall be evaluated) is very long. Not compared to the thousands of characters some people fling at PCRE. :-) I am not a PHP user; from what you posted, I am not sure that I extracted the final string that would be passed to PCRE. > Hence the error depends on the combination apache - php - pcre I deal only with PCRE; I don't know or use apache or php. I have tried to run the match directly using pcretest, but as I said above, I am not at all sure I had the right data. Combination errors usually need the attention of the most downstream maintainer - in this case, probably PHP. Have you reported this to the PHP people? If you can provide a pattern and a data string that cause PCRE to misbehave in some way, then I will certainly look at it. Philip -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at http://lists.exim.org/mailman/listinfo/pcre-dev
