On 2013-03-11 20:00, Jan Beich wrote: > Dimitry Andric <d...@freebsd.org> writes: > >> $ echo 'sub/foo.barx' | grep sub/foo.bar >> $ echo $? >> 1 > > $ echo 'sub/foo.barx' | env -i grep sub/foo.bar > $ echo 'sub/foolbarx' | env -i grep sub/foo.bar > $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' > sub/foo.barx > $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar > sub/foo.bar > $ echo 'sub/foo.barx' | env -i grep --color=no sub/foo.bar > sub/foo.barx > > A buggy shortcut?
No, after some digging in and debugging of the bsdgrep code, I found out it is a regression caused by r246917, which is a fix for "bin/175213: [patch] bsdgrep(1) segfaults upon malicious input". If you revert it, bsdgrep starts working correctly again. I think it would be best to back out r246917 for now, until the regression can be fixed properly. Having bsdgrep crash is bad, but not returning any results while it should is even worse... _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
