I hope it's fixed for newer versions, here what I tried for reproduction:
Just taking the code from alarm and embedding (dummy) code into a long running regex
Generally I try to avoid alarm...
use strict;
use warnings;
my $start;
my $diff;
my $timeout;
sub tst {
$timeout=shift;
my $str = "a"x10000;
$str .= "b";
eval {
local $SIG{ALRM} = sub { die "alarm\n" }; # NB: \n required
alarm $timeout;
$str =~ /^ (( a*
(?{1}) # dummy code
)*)* $/x;
alarm 0;
};
if ($@) {
die unless $@ eq "alarm\n"; # propagate unexpected errors
die "timed out after $timeout sec :". time();
}
else {
print "normal";
}
}
tst($_) for 2;
output
Complex regular subexpression recursion limit (32766) exceeded at /hom
+e/lanx/B/PL/PM/timeout_regex.pl line 18.
Compilation segmentation fault at Fri May 30 17:41:48
Cheers Rolf
( addicted to the Perl Programming Language)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.