tag 23763 notabug thanks On 06/13/2016 01:45 PM, Bjoern Voigt wrote: > Grep shows a bug, if it processes a text file with at least one embedded > 0 (ASCII zero) character after byte 32768.
Thanks for the report. However, this is not a bug in grep, but documented behavior. By definition, a text file CANNOT contain NUL bytes; any file with NUL characters is a binary file. You can still make grep process it as a text file, but only with the '-a' flag. > Grep stops with the error > message "Binary file testfile.txt matches" and exit code 0. The error > message is written to standard output. Any line after the 0 character is > silently ignored in output. POSIX allows this behavior, in that it says that grep's behavior is undefined on non-text files (which you have by virtue of your NUL byte). Since this is documented behavior of GNU grep when -a is not used, I'm closing this as not a bug. But feel free to add further comments to this thread. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
