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
Bleadperl v5.27.0-132-g13f4dd346e breaks JDDPAUSE/MarpaX-Languages-M4-0.017.tar.gz #16049
Comments
From @andkSlaven digged it out, the second on this day, delightfully hard to track. bisect commit 13f4dd3 Forbid out of range Unicode code points. diagnostics Note: no evidence available for threaded perls; you need not try because : t/m4.t ................. 73/? perl -V Summary of my perl5 (revision 5 version 27 subversion 1) configuration: Characteristics of this binary (from libperl): -- |
From @khwilliamsonI'll take a look at this. |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonOn Tue, 27 Jun 2017 12:27:03 -0700, khw wrote:
I have traced this down to these lines in the distro: use re::engine::GNU 0.019; And, the GNU engine as interpreted by re::engine::GNU is calling back to Perl's utf8_to_uvchr() with code points that are no longer legal because they are above IV_MAX, in particular 0xFF...FF80. (I lost track of how many F's, and its not important enough to figure it out.) If I use Perl's engine by commenting out the 'use re...', this error doesn't happen, though other failures occur, due presumably to the differences in semantics in GNU's. A backtrace yields: (gdb) bt Stack position #5 0x00007fffeec0d10a in rpl_Perl_isalnum (c=18446744073709551488) indicates that the re::engine function rpl_Perl_isalnum() is being called with a code point (c=) that is now illegal in perl. It calls the perl function Perl__is_uni_FOO, which no longer accepts this input value. So this is the problem. Perl calls the substitute engine in frame #13, and it calls functions within itself until the call at #4. (It has its own regcomp.c, so that isn't ours in those frames.) At this point, I'm uncertain what to do. I'm pretty sure this isn't Perl's bug. We deprecated use of these code points for 2 cycles, and now they're illegal. -- |
From @jkeenanOn Wed, 26 Jul 2017 16:31:02 GMT, khw wrote:
If that's the case, then can you open a bug ticket at https://rt.cpan.org/Dist/Display.html?Name=MarpaX-Languages-M4? Thank you very much. -- |
From @khwilliamsonOn 07/26/2017 04:53 PM, James E Keenan via RT wrote:
Now done |
From @khwilliamsonThe owner has already issued a fix for this, in re::engine::GNU 0.022. I have tested it, and the test no longer fails. -- |
@khwilliamson - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#131663 (status was 'resolved')
Searchable as RT131663$
The text was updated successfully, but these errors were encountered: