(In reply to Vincent Lefèvre from comment #19) > regbug.c is derived from the attachment in Bug#17356 (as said in comment 5). > I've tested this original testcase: with glibc 2.34 on x86_64, it crashes > (segmentation fault); with glibc 2.35 on riscv64 (host gcc92), it outputs > "no match (incorrect)". > > So it seems that the fix mentioned in comment 13 fixed the crashes (which > was the initial bug report), but not the misbehavior.
OK, so in that case how about if we update Bug#17356 by (1) saying it is no longer a duplicate of Bug#11053 (as we've fixed the latter but not the former), and (2) reopening Bug#17536? If I understand you correctly, that would match the symptoms you describe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
