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

Previous Next

Package: grep;

Reported by: mega lith01 <megalith01 <at> gmail.com>

Date: Thu, 30 Mar 2023 20:01:02 UTC

Severity: normal

Tags: patch

Merged with 60690, 62605

To reply to this bug, email your comments to 62552 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-grep <at> gnu.org:
bug#62552; Package grep. (Thu, 30 Mar 2023 20:01:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to mega lith01 <megalith01 <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-grep <at> gnu.org. (Thu, 30 Mar 2023 20:01:02 GMT) Full text and rfc822 format available.

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

From: mega lith01 <megalith01 <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: Bug found in latest stable release v3.10 of grep
Date: Thu, 30 Mar 2023 17:01:27 +0100

[Message part 1 (text/plain, inline)]
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.

Many Thanks!.

[Message part 2 (text/html, inline)]
[grep-310-bug.sh (text/x-sh, attachment)]
Information forwarded to bug-grep <at> gnu.org:
bug#62552; Package grep. (Fri, 31 Mar 2023 14:18:01 GMT) Full text and rfc822 format available.

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
Merged 62552 62605. Request was from Paul Eggert <eggert <at> cs.ucla.edu> to control <at> debbugs.gnu.org. (Sun, 02 Apr 2023 18:33:02 GMT) Full text and rfc822 format available.
Merged 60690 62552 62605. Request was from Paul Eggert <eggert <at> cs.ucla.edu> to control <at> debbugs.gnu.org. (Mon, 03 Apr 2023 20:45:02 GMT) Full text and rfc822 format available.
This bug report was last modified 1 year and 30 days ago.

Previous Next

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