newsgrep - News: grep-2.24 released [stable]

Latest News
grep-3.7 released [stable] posted by meyering, Sat 14 Aug 2021 08:12:52 PM UTC - 0 replies
grep-3.6 released [stable] posted by meyering, Mon 09 Nov 2020 05:33:39 AM UTC - 0 replies
grep-3.5 released [stable] posted by meyering, Mon 28 Sep 2020 03:30:42 AM UTC - 0 replies
grep-3.4 released [stable] posted by meyering, Thu 02 Jan 2020 10:32:07 PM UTC - 0 replies
grep-3.3 released [stable] posted by meyering, Fri 21 Dec 2018 04:51:38 AM UTC - 0 replies
[Submit News]
[38 news in archive]

grep-2.24 released [stable]

Item posted by Jim Meyering <meyering> on Fri 11 Mar 2016 06:01:22 AM UTC.

This is to announce grep-2.24, a stable bug-fix-only release.
This release, so soon after 2.23, was prompted by the discovery
of two bugs related to the --null-data (-z) option.
These bugs were introduced in 2010 and 2002 respectively.

There have been 8 commits by 2 people in the 5 weeks since 2.23.

See the NEWS below for a brief summary.

Thanks to everyone who has contributed!
The following people contributed changes to this release:

  Jim Meyering (7)
  Paul Eggert (1)

Jim [on behalf of the grep maintainers]

Here is the GNU grep home page:

For a summary of changes and contributors, see:;a=shortlog;h=v2.24
or run this command from a git-cloned grep directory:
  git shortlog v2.23..v2.24

Here are the compressed sources and a GPG detached signature[*]:

Use a mirror for higher download bandwidth:

[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact.  First, be sure to download both the .sig file
and the corresponding tarball.  Then, run a command like this:

  gpg --verify grep-2.24.tar.xz.sig

If that command fails because you don't have the required public key,
then run this command to import it:

  gpg --keyserver --recv-keys 7FD9FCCB000BEEEE

and rerun the 'gpg --verify' command.

This release was bootstrapped with the following tools:
  Autoconf 2.69.147-5ad35
  Automake 1.99a
  Gnulib v0.1-697-gcd6a452


* Noteworthy changes in release 2.24 (2016-03-10) [stable]

** Bug fixes

  grep -z would match strings it should not.  To trigger the bug, you'd
  have to use a regular expression including an anchor (^ or $) and a
  feature like a range or a backreference, causing grep to forego its DFA
  matcher and resort to using re_search.  With a multibyte locale, that
  matcher could mistakenly match a string containing a newline.
  For example, this command:
    printf 'a\nb\0' | LC_ALL=en_US.utf-8 grep -z '^[a-b]*b'
  would mistakenly match and print all four input bytes.  After the fix,
  there is no match, as expected.
  [bug introduced in grep-2.7]

  grep -Pz now diagnoses attempts to use patterns containing ^ and $,
  instead of mishandling these patterns.  This problem seems to be
  inherent to the PCRE API; removing this limitation is on PCRE's
  maint/README wish list.  Patterns can continue to match literal ^
  and $ by escaping them with \ (now needed even inside [...]).
  [bug introduced in grep-2.5]

No messages in grep-2.24 released [stable]


Back to the top

Powered by Savane 3.9