<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote
cite="mid:20170129182425.frbrjthreezf3wll@estella.local.invalid"
type="cite">
<pre wrap="">This still happens with 5.24.1-1. It can be reduced to
printf "\x9c\x5a" | perl -CI -ne '/[^#]*/'
The byte sequence is indeed invalid utf8 (as shown by iconv as well),
but you're explicitly telling Perl (with -CS) that it's getting utf8 on
stdin. This is a recipe for problems.
So I'm not sure if it's a bug at all. At most the failure should be
handled a bit more gracefully.
</pre>
</blockquote>
<br>
This should be warning, warning programmer could turn off. It's very
rare that perl just dies because data it handles is not as expected.
<br>
Wrong data? Ok, fine, warn, and go on processing. <br>
<br>
Strange is that /[^#]*/ dies, while /(.*)/ doesn't == in both cases
data is the same, data is wrong. Sometimes perl dies, sometimes not.
<br>
<br>
</body>
</html>