Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Re^7: Fatal code point 0xFFFFFFFFFFFFFFFF

by Anonymous Monk
on Sep 09, 2018 at 23:00 UTC ( #1222008=note: print w/replies, xml ) Need Help??


in reply to Re^6: Fatal code point 0xFFFFFFFFFFFFFFFF
in thread Fatal code point 0xFFFFFFFFFFFFFFFF

If you're feeding codepoints > 0x7fffffffffffffff into perl, something fairly major has gone wrong, and quietly ignoring those rogue codepoints is just masking the bigger issue.

This excellent sentence got me pointed in the right direction! Thank you. Here's what the regex engine was freaking out about:

Encode::decode(utf8 => $binary_data) # from binmode filehandle
Matching that data triggers the fatal code point error, but only if the regex fails to match a string (numbers seem to match or fail quietly). Different versions of perl give different results.

Perl 5.26.2:

perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(f)/i;'
F
perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(fu)/i;'
fu
perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(fub)/i;'
Operation "pattern match (m//)" returns its argument for UTF-16 surrogate U+DFA8 at -e line 1.

Operation "pattern match (m//)" returns its argument for non-Unicode code point 0x1C9140 at -e line 1.

Operation "pattern match (m//)" returns its argument for non-Unicode code point 0xE6BAAA at -e line 1.

Use of code point 0xFFFFFFFFFFFFFFFF is deprecated; the permissible max is 0x7FFFFFFFFFFFFFFF. This will be fatal in Perl 5.28 in pattern match (m//) at -e line 1.

Use of code point 0xFFFFFFFFFFFFFFFF is deprecated; the permissible max is 0x7FFFFFFFFFFFFFFF. This will be fatal in Perl 5.28 at -e line 1.

Operation "pattern match (m//)" returns its argument for non-Unicode code point 0xFFFFFFFFFFFFFFFF at -e line 1.


Perl 5.28:
perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(f)/i;'
f
perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(fu)/i;'
Operation "pattern match (m//)" returns its argument for UTF-16 surrogate U+DFA9 at -e line 1.

FU


perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(fub)/i;'
Operation "pattern match (m//)" returns its argument for UTF-16 surrogate U+DFA9 at -e line 1.

Operation "pattern match (m//)" returns its argument for non-Unicode code point 0x1CB760 at -e line 1.

Operation "pattern match (m//)" returns its argument for non-Unicode code point 0x18B14C at -e line 1.

Operation "pattern match (m//)" returns its argument for non-Unicode code point 0x7FFFFFFFFFFFFFFF at -e line 1.


Numbers:
perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(1)/i;'
1
perl -MEncode -le 'open my $fh, "<", $^X; binmode $fh; local $/ = unde +f; my $data = <$fh>; close $fh; $data = Encode::decode(utf8 => $data) +; print $1 if $data =~ /(666)/i;'

Replies are listed 'Best First'.
Re^8: Fatal code point 0xFFFFFFFFFFFFFFFF
by dave_the_m (Monsignor) on Sep 10, 2018 at 07:14 UTC
    It's not clear to me what point you're trying to make with the code examples.

    Dave.

      It's not clear to me what point you're trying to make with the code examples.

      A fatal code point Dave! :-) Next time someone accidentally tries to decode a binary file with Encode and Perl complains about fatal code points they may find this node and save the day it took me to figure out what was wrong. Then the fix is easy.

        You mean, you read data that was not UTF-8?

        This is what was told to you here and here and here, so I must still misunderstand what your problem is, and how you solved it.

        Maybe you can explain in a bit longer text what the problem was.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1222008]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (2)
As of 2019-06-16 05:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Is there a future for codeless software?



    Results (76 votes). Check out past polls.

    Notices?