GNU bug report logs - #18455
grep 2.20 perl-regexp: invalid UTF-8 byte sequence in input

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18455 in the body.
You can then email your comments to 18455 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mario Grgic <veritas.divina <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: grep 2.20 perl-regexp: invalid UTF-8 byte sequence in input
Date: Thu, 11 Sep 2014 21:27:22 -0400

This happens with GNU grep version 2.20 and PCRE 8.35 on Mac OS X. The following command reproduce the problem: 

$ printf 'j\x82\nj\n' | grep -P j
invalid UTF-8 byte sequence in input

But I usually encounter this when recursively searching through files and encountering a binary file which contains invalid UTF-8 sequence.  If binary file with invalid UTF-8 sequence is encountered first (without any other matches), grep will abort the entire recursive search and not even mention which file caused the error. This is somewhat confusing when you first encounter it. 

By the way, this works in GNU grep 2.18 without any errors (you get messages like binary file x matches), and with PCRE 8.33 or 8.35 (I have not tried any other combinations). 

Message #8 received at 18455 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Mario Grgic <veritas.divina <at> gmail.com>
Cc: 18455 <at> debbugs.gnu.org
Subject: grep 2.20 perl-regexp: invalid UTF-8 byte sequence in input
Date: Thu, 11 Sep 2014 20:40:35 -0700

This appears to be the same as Bug#18266:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18266

which means it's fixed in the master version and the fix should appear 
in the next release.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.