https://bugs.exim.org/show_bug.cgi?id=1916

Markus Elfring <elfr...@users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86                         |x86-64

--- Comment #1 from Markus Elfring <elfr...@users.sourceforge.net> ---
(In reply to comment #0)

I got the impression that the message “regular expression is too 
complicated”
is connected with the internal identifier “ERR86”.
I added logging statements at a few source code places after it is assigned to
variables like “errorcode”. So it seems that an error message was displayed
beccause the function “could_be_empty_branch” returned a negative value 
from a
call in “pcre2_compile_8”.


How are the chances to reconsider this software limitation (and a corresponding
comment there)?

http://vcs.pcre.org/pcre2/code/trunk/src/pcre2_compile.c?revision=596&view=markup
:
“…
Setting the cap at 1100 allows the test for more than 1023 capturing patterns
to work.
…”


I changed this value to “3456” for another test try. My constructed search
pattern was finally accepted then. The successful test display contained
expected data.
Is an information like “Memory allocation (code space): 102475” also worth 
for
further considerations here?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev 

Reply via email to