bug#18806: grep -rP getline crashes prematurely (without displaying all results) on invalid UTF-8 input with LC_ALL=en_US.UTF-8

[Paul Eggert]

Jim Meyering wrote:
> after your change,
> our pcre-invalid-utf8-input hangs. That happens because the following
> infloops (stuck in pcre_exec) on a CentOS6 system:
>
>    printf 'j\202j\nj\nk\202\n' > in; LC_ALL=en_US.utf8 src/grep -P 'k$' in
>
> That binary was linked with the libpcre from this package:
>
>    pcre-7.8-4.el6.x86_64

I'm getting a failure in pcre-invalid-utf8-input both before and after the 
change, with CentOS 6.5 and pcre-7.8-6.el6.x86_64.  In my case the failures are 
segmentation violations; perhaps 7.8-4 has a different failure mode, or perhaps 
there's some other minor change to your platform that causes libpcre to infloop. 
 Either way, this appears to be a PCRE bug that grep can't be expected to work 
around.

Does the attached patch cause the test to fail reliably for you, instead of 
looping?

By the way, I'm not sure why tests distinguish between require_en_utf8_locale_ 
and require_compiled_in_MB_support; the latter requires the former, and there's 
no point requiring the former unless we also require the latter.

pcre.diff
Description: Text document