Perl segfaults with a regex_sets error message #14851
Comments
From @dcollinsnThe search on this bug tracker doesn't seem to search issue descriptions, but in any event I can't figure out how to tell if this is a duplicate or not. Searches for the test case, regex_sets, segfault, and the first bad revision id didn't reveal any obvious duplicates. Test case is the 12-byte file: 00./(?[()])/ dcollins@nagios:/usr/local/perl-afl/out/allcrash$ ../../bin/perl -w f2i000041 Git bisect revealed: 6798c95 is the first bad commit Change /(?[...]) to have normal operator precedence :100644 100644 ce36c6c64ad7f52f32f18c3af5faea7782e77f8f a909f7d5bc6cacd8ecd0e292d17587460c2dabf5 M embed.fnc dcollins@nagios:/usr/local/perl-afl/out/allcrash$ ../../bin/perl -V Characteristics of this binary (from libperl): (gdb) run Program received signal SIGSEGV, Segmentation fault. ==1344== Memcheck, a memory error detector |
From @khwilliamsonThanks for reporting this. I'll fix it |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonThanks for finding and reporting this. Now fixed in blead by commit |
@khwilliamson - Status changed from 'open' to 'pending release' |
@mauke - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#125805 (status was 'resolved')
Searchable as RT125805$
The text was updated successfully, but these errors were encountered: