Date: Mon, 29 Sep 2014 23:05:09 +0200 From: Stefan Ehmann <shoesoft@gmx.net> To: Mark Felder <feld@FreeBSD.org> Cc: freebsd-stable@freebsd.org, gabor@FreeBSD.org Subject: Re: xzgrep: incomplete results on larger files Message-ID: <5429C985.4090806@gmx.net> In-Reply-To: <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com> References: <541DE9FC.2090003@gmx.net> <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29.09.2014 16:14, Mark Felder wrote: > > > On Sat, Sep 20, 2014, at 15:56, Stefan Ehmann wrote: >> I observed the following behavior on 10.1-BETA1 r271683M (amd64): >> >> xzgrep doesn't search the complete file: >> $ seq 10000 | xz > seq.xz >> $ xzgrep -c . seq.xz >> 6775 >> >> Using regular grep works as expected: >> $ xzcat seq.xz | grep -c . >> 10000 >> >> Processing seems to stop after 32KB (uncompressed). >> > > Wow, this is bizarre... Compression with xz is getting more and more > popular. This may have bit me a few times and I didn't even know it! > > I'll see what I can to do bring this to someone's attention. I've looked further into this issue. The original approach could never have worked since the xz library was used incorrectly. I came up with this patch today: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186861 It's getting late. So it's not tested very much and might contain bugs. -- Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5429C985.4090806>