[Bug 1940996]

[Paul Eggert]

On 9/5/22 18:06, vincent-srcware at vinc17 dot net wrote:
>
> What is the status of this bug? The comment says that it is fixed, and I could
> check on an Ubuntu 22.04.1 LTS machine with libc6 2.35-0ubuntu3.1 that regbug.c
> and rebug2.c no longer fail, but the result is still incorrect with the grep
> example from Debian bug 884075:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884075
>
> vinc17 at gcc92:~$ echo 11111111111 | grep -E '^(11+)\1+$|^1?$' ; echo $?
> 11111111111
> 0
>
It looks like my comment 
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884075#27> was 
incorrect, in that the two bugs are different bugs. glibc bug 11053 is 
fixed, but Debian bug 884075 is not fixed. Perhaps a better match for 
Debian bug 884075 is glibc bug 10844.

It's not an important bug. However, if you have time to fix it please 
feel free to send in a fix.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1940996

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+subscriptions