From owner-freebsd-current@FreeBSD.ORG  Mon Mar 11 21:05:54 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 6E131E35;
 Mon, 11 Mar 2013 21:05:54 +0000 (UTC) (envelope-from dim@FreeBSD.org)
Received: from tensor.andric.com (tensor.andric.com
 [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26])
 by mx1.freebsd.org (Postfix) with ESMTP id 2DBBB15C;
 Mon, 11 Mar 2013 21:05:54 +0000 (UTC)
Received: from coleburn.home.andric.com (coleburn.home.andric.com
 [192.168.0.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
 (No client certificate requested)
 by tensor.andric.com (Postfix) with ESMTPSA id 8E9825C44;
 Mon, 11 Mar 2013 22:05:50 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error:
 configure: error: no usable dependency style found
From: Dimitry Andric <dim@FreeBSD.org>
In-Reply-To: <1UF7wX-000BVL-0y@internal.tormail.org>
Date: Mon, 11 Mar 2013 22:05:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org>
References: <513B56E8.2060702@zedat.fu-berlin.de>
 <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org>
 <20130309233930.GA95285@troutmask.apl.washington.edu>
 <513DAF4F.50602@FreeBSD.org>
 <20130311131318.GA57506@troutmask.apl.washington.edu>
 <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org>
 <1UF7wX-000BVL-0y@internal.tormail.org>
To: Jan Beich <jbeich@tormail.org>
X-Mailer: Apple Mail (2.1499)
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 =?iso-8859-1?Q?G=E1bor_K=F6vesd=E1n?= <gabor@FreeBSD.org>,
 freebsd-ports@freebsd.org, Niclas Zeising <zeising+freebsd@daemonic.se>,
 "O. Hartmann" <ohartman@zedat.fu-berlin.de>, Mark Johnston <markj@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 21:05:54 -0000

On 2013-03-11 20:00, Jan Beich wrote:
> Dimitry Andric <dim@FreeBSD.org> writes:
>=20
>> $ echo 'sub/foo.barx' | grep sub/foo.bar
>> $ echo $?
>> 1
>=20
> $ 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=3Dno sub/foo.bar
> sub/foo.barx
>=20
> 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...