-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault / strange match with recursive subpattern (?0) #15228
Comments
From lorenz@math.tu-berlin.deThis is a bug report for perl from lorenz@math.tu-berlin.de, Since the rework related to #126182, the recursive pattern below causes perlblead to segfault. We observed test failures for our software since March 8. There is also a related (probably) invalid match listed further below. The pattern is almost the same as on 'perlre', except that I replaced (?-1) by (?0). Changing that to (?1) fixes the segfault but should not really make any difference as far as I can see. Segfaulting expression:
Compiling REx "(\((?:[^()]++|(?0))*+\))" EXECUTING... Matching REx "(\((?:[^()]++|(?0))*+\))" against "((5maa-maa)(maa-3maa))" Program received signal SIGSEGV, Segmentation fault. Another odd thing appears if you remove the possessiveness from both matches, I do not think that the result is valid for the pattern. Again, changing to (?1) makes it work, i.e. match the full string.
EXECUTING... Matching REx "(\((?:[^()]+|(?0))*\))" against "((5maa-maa)(maa-3maa))" Flags: Site configuration information for perl 5.23.9: Configured by lorenz at Mon Mar 14 10:48:06 CET 2016. Summary of my perl5 (revision 5 version 23 subversion 9) configuration: @INC for perl 5.23.9: Environment for perl 5.23.9: |
From @demerphqOn 14 March 2016 at 12:03, via RT <perlbug-followup@perl.org> wrote:
Thank you very much for the report, and sorry for the inconvenience caused.
That strongly suggests to me what I did wrong. I will do the best I can to get to the bottom of this. Thanks a lot, |
The RT System itself - Status changed from 'new' to 'open' |
From @demerphqI believe I have fixed both the issues reported in this ticket. If the Yves |
From lorenz@math.tu-berlin.deBoth reported issues (and the original issue in our code) are fixed with Thanks a lot for the quick response and fix, |
From @demerphqOn 15 March 2016 at 08:51, l.mai@web.de via RT
d1c49ad was helpful in understanding the bug, but was not directly -- |
From @demerphqOn 15 March 2016 at 10:56, Benjamin Lorenz <lorenz@math.tu-berlin.de> wrote:
Thanks for the report, and for running bleading edge perls for testing. It is very helpful. cheers, -- |
@iabyn - Status changed from 'open' to 'pending release' |
From @khwilliamsonThank you for submitting this report. You have helped make Perl better. Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0 |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#127705 (status was 'resolved')
Searchable as RT127705$
The text was updated successfully, but these errors were encountered: