GNU bug report logs - #62552
Bug found in latest stable release v3.10 of grep

Previous Next

Full log

Message #8 received at 62552 <at> debbugs.gnu.org (full text, mbox):

From: Jeffrey Walton <noloader <at> gmail.com>
To: mega lith01 <megalith01 <at> gmail.com>
Cc: 62552 <at> debbugs.gnu.org
Subject: Re: bug#62552: Bug found in latest stable release v3.10 of grep
Date: Fri, 31 Mar 2023 10:16:44 -0400

On Thu, Mar 30, 2023 at 4:01 PM mega lith01 <megalith01 <at> gmail.com> wrote:
>
> Hi, i have identified what looks to be a bug in grep v3.10, the bug is not
> present in v3.8 or v3.9, to reproduce the bug please see the attached bash
> script.
>
> The bug looks related to the use of the regex [^\d]+ which then ends up
> resulting in no match.
>
> If you need any more details then please let me know, I am very keen to get
> this bug squashed as I make heavy use of grep in my scripts.

This appears to be an issue caused by PCRE2. The GNU Grep folks have
been discussing it on their mailing list. See "Possible regression in
grep 3.10", https://lists.gnu.org/archive/html/grep-devel/2023-03/msg00017.html.

Jeff

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.