From owner-freebsd-stable@freebsd.org Sat Jan 21 10:09:32 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A839CCBA6EC for ; Sat, 21 Jan 2017 10:09:32 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08844171B for ; Sat, 21 Jan 2017 10:09:31 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from walrus.pepperland ([81.217.70.96]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M6P5z-1cJFZs0uGR-00yNHb; Sat, 21 Jan 2017 11:09:19 +0100 Subject: Re: unexpected grep -o behavior To: Kyle Evans References: Cc: FreeBSD-STABLE Mailing List From: Stefan Ehmann Message-ID: Date: Sat, 21 Jan 2017 11:09:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:1Q5JdILYXhapCkWlyFV17vr1Og/56lrje7TPffYArlRQBkSIrxg DRg7HRCDjYVFzptRTxJcZjg68ZSnD70q23Z7W5DD6Ye/5U5Fbtk35R3D+BPIzRaxsADP/5R DKzjQ9FHXAawoA1rWSaBU/FVYyzFMQVhHp9YhHQ1/5vGhyeqRmhx0AL83jbBEvC1G7WQG83 HBJyb3vysu9coIYpS3WAg== X-UI-Out-Filterresults: notjunk:1;V01:K0:qolua21YE2s=:IGMRHCcs5IL7rCvN1hERx2 EkqU9OLH1Pww3IArkQLnM8KOX789T5yxRJjoNkvjyD0op1vfn+x6UCXKsfhNvDVFvAkKMNLJp dEyKu8MzKwmvaHF1S9brJRu3h6S3MtTH+xIDMbKDZsyOohuHXM2r2dToFeFNlQx98s7OE0kPN 5eaIsEnjVlfIfDXmJm1rjRiT0F0iDhEqCn3QwDpL1by86vwn+ya58+EL8DkHfJdto8eJ0q3Rm Ea6S+gJD8mx3s8T/APDXMP0kaU3fub02BI37gvYZePTbU6YrbXpQLRe8fQdYIr9GVoPYag7Rb FYf7Z4dAEI85qMmhm15NKfI6pRcoA4bn4AtX+Qngc2BsQcaNmMrTH706Qra6Bipe1ZRDvfD7Q M3ZylPYsZwLr+rLXaKhzUslEOkA8aohvwtbcWvUQPYmq0H20o6kRk1GxtrjdaLYHa5FHCsNeO W/JIowNKVKjuqjZxfnWkv0Sf7eypSofznp2y8lJVAHNdeI6QrY4fJdSvc0kmZEV9eHGsp0cMx MecQh6EnXpqsA3OO4yIlywU/yRWuJ5UDZpfQjUTgsHDKinjt7LWmOSDzXaK8pzTGBX/roH1LC 67gkNWt4Xv8XnMSX01by6uN9Jp/Go+C57NU+/o4iKN0WVU+7R9LkCAg1QmMkSWQAtbGn233nv +yyXb/qRr1KiGohbWxpj3i2oWArGLwjwmYfwUwzW8SSvRGgz3e2Cfk2OhUMR/FzF7qG/nrtOx W3oBv0YZ5WVVeLPQSO/2zrsRdinR/j7Tooe4WMgGxK6QGRq4Hr9Bxw4ooUCc8ucak8aFdxUtC 1IdagiR X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2017 10:09:32 -0000 On 21.01.2017 07:28, Kyle Evans wrote: > On Sun, Nov 27, 2016 at 2:52 PM, Stefan Ehmann wrote: >> Bug 195763 looks related, but I'm not sure it's the same issue. > > Hi, > > FYI- that bug is only tangentially related, but I've updated my patch > to also address it while I'm in the neighborhood of where this problem > was. See Comment #5 if you're interested in a more detailed > explanation. Thanks a lot for taking care of this bug. bsdgrep now works for my testcase. As a side note: On 11.0-RELEASE (GNU) grep in base suffers the same bug. I tried version 2.20 on Debian which works correctly. But I assume it won't get updated due to GPLv3. Makes me wonder if we still need two grep variants in base.