Re: Non capturing parenthesis in regexp causes seg fault.

Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1213196608

Re: Non capturing parenthesis in regexp causes seg fault.

Alan DeKok wrote: Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... It is... It allows you to create backreferences but not

Re: Non capturing parenthesis in regexp causes seg fault.

Arran Cudbard-Bell wrote: Alan DeKok wrote: Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... It is... It allows you to create

Non capturing parenthesis in regexp causes seg fault.

Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ } --- ++? if (%{User-Name} =~ /(?:.*)/) expand: %{User-Name} - anonymous Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1213196608 (LWP 6433)] 0xb7bc9492 in regexec () from

Re: Non capturing parenthesis in regexp causes seg fault.

Arran Cudbard-Bell wrote: Arran Cudbard-Bell wrote: Alan DeKok wrote: Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... It is...