This is for: * correctness regressions compared to grep-2.5.1-31 * performance regressions compared to grep-2.5.1-31 * benchmark results * even a simple "installed it here and it seems to work"
grep -f and fgrep fail on binary files at read(3, "eck\0freopen\0__wuflow\0re_search\0f"..., 12288) = 12288 open("/usr/lib/gconv/gconv-modules.cache", O_RDONLY) = 4 fstat64(4, {st_mode=S_IFREG|0644, st_size=21544, ...}) = 0 mmap2(NULL, 21544, PROT_READ, MAP_SHARED, 4, 0) = 0xf6ddc000 close(4) = 0 And there is sits as long as I'm willing to wait (up to an hour so far). Doesn't matter whether I'm root or a user. Strings file|grep <something> doesn't show this problem, nor does it occur on ascii files.
Thanks for the report. This seems to be a regression relative to FC3. Here is the command line that reproduces it: fgrep foo /bin/ex (/bin/ex from vim-minimal-6.3.030-3)
Fixed package is grep-2.5.1-31.2. Please re-test. Thanks!
Works now. Thanks!
Just wanted to mention that grep_2.5.1-40_i386.rpm from rawhide shows the same regression.
Yes, I fixed rawhide at the same time.