Re: regex-related segfault in mod_include

2009-02-27 Thread Lars Eilebrecht
Ruediger Pluem wrote: What are the values of idx re-match[idx].rm_so re-match[idx].rm_eo re-source and what is the string re-source is pointing to when the crash happens? idx is 1 and re-source points to an empty string which is fine. However, re-match[idx].rm_so and

AW: regex-related segfault in mod_include

2009-02-27 Thread Plüm, Rüdiger, VF-Group
-Ursprüngliche Nachricht- Von: Lars Eilebrecht [mailto:l...@eilebrecht.net] Gesendet: Freitag, 27. Februar 2009 12:54 An: dev@httpd.apache.org Betreff: Re: regex-related segfault in mod_include Ruediger Pluem wrote: What are the values of idx re-match[idx].rm_so re

Re: regex-related segfault in mod_include

2009-02-27 Thread Lars Eilebrecht
Plüm, Rüdiger, VF-Group wrote: However, re-match[idx].rm_so and re-match[idx].rm_eo are random numbers, i.e., a garbage value (I guess they should be 0 if there was no match?). IMHO they should be -1. Right, that actually makes more sense ... We use different PCRE versions in

regex-related segfault in mod_include

2009-02-26 Thread Lars Eilebrecht
Hi, the following SSI statements triggers a segfault when QUERY_STRING is empty (tested with 2.2.11): !--#if expr=$QUERY_STRING = /foobar=([0-9]+)$/ -- !--#set var=foobar value=$1 -- !--#else -- !--#set var=foobar value=$1 -- !--#endif -- I tracked this down to

Re: regex-related segfault in mod_include

2009-02-26 Thread Ruediger Pluem
On 02/26/2009 07:58 PM, Lars Eilebrecht wrote: Hi, the following SSI statements triggers a segfault when QUERY_STRING is empty (tested with 2.2.11): !--#if expr=$QUERY_STRING = /foobar=([0-9]+)$/ -- !--#set var=foobar value=$1 -- !--#else -- !--#set var=foobar value=$1 --