The release/2.34/master branch has been updated by Florian Weimer
:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=86a701a20479dfbc23540b3143fd5b28660a2447
commit 86a701a20479dfbc23540b3143fd5b28660a2447
Author: Paul Eggert
Date: Tue Sep 21 07:47:45 2021 -0700
regex: copy back from G
(In reply to eggert from comment #24)
> Sure, feel free to file it as a new bug.
Bug 29560.
--
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
What about attachment 10674 ("This test case silently returns the wrong
answer"), with the pattern "^(11+)\\1+$|^1?$" and the string
"1"?
Should it be regarded as part of Bug#17356 or another bug? This case
seems quite different from Bug#10844 and Bug#17356. Unless the intent is
to gro
Sure, feel free to file it as a new bug.
--
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 gre
(In reply to Vincent Lefèvre from comment #21)
> (In reply to eggert from comment #20)
> > 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
** Changed in: grep
Status: In Progress => Fix Released
--
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
(In reply to eggert from comment #20)
> 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 des
(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 (incorre
(In reply to Vincent Lefèvre from comment #16)
> (In reply to eggert from comment #15)
> > glibc bug 11053 is fixed,
>
> Shouldn't this bug be resolved as fixed, then?
OK, done.
> > Perhaps a better match for
> > Debian bug 884075 is glibc bug 10844.
>
> It seems different.
In that case it m
Sorry, actually both regbug.c and rebug2.c fail as they return the exit
status 1 (with my usual configuration, my prompt shows any non-zero exit
status, but this is not the case of the machine on which I had done the
test, so that I missed the failure initially):
vinc17@gcc92:~$ ./regbug
vinc17@gc
(In reply to eggert from comment #15)
> glibc bug 11053 is fixed,
Shouldn't this bug be resolved as fixed, then?
> but Debian bug 884075 is not fixed. Perhaps a better match for
> Debian bug 884075 is glibc bug 10844.
It seems different. With Debian bug 884075, the "|^1?$" part is
important (it
This could be simplified a bit:
vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$|^$'
111
(nothing colored).
--
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.ne
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
** Bug watch added: Debian Bug tracker #884075
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884075
--
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
(In reply to cvs-com...@gcc.gnu.org from comment #13)
> The master branch has been updated by Paul Eggert :
>
> https://sourceware.org/git/gitweb.cgi?p=glibc.git;
> h=0b5ca7c3e551e5502f3be3b06453324fe8604e82
>
> commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82
> Author: Paul Eggert
> Date: Tue
Naively dropping this commit into the glibc package yields a dozen test
failures.
FAIL: conform/POSIX2008/regex.h/conform
FAIL: conform/POSIX/regex.h/conform
Buildlog with different results from my PPA build
https://launchpadlibrarian.net/559561150/buildlog_ubuntu-impish-amd64.glibc_2.34-0ubuntu3~ppa1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
h
The master branch has been updated by Paul Eggert
:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0b5ca7c3e551e5502f3be3b06453324fe8604e82
commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82
Author: Paul Eggert
Date: Tue Sep 21 07:47:45 2021 -0700
regex: copy back from Gnulib
C
Did the patch ever get sent to libc-alpha?
--
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:
In Progress
Status in gr
(In reply to Michael Hudson-Doyle from comment #11)
> Did the patch ever get sent to libc-alpha?
Unfortunately I never got around to it.
Someone else can shepherd it if it's urgent; otherwise I suppose it can
wait until someone gets around to syncing Gnulib with glibc.
--
You received this bug
Launchpad has imported 11 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=11053.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://
Public bug reported:
'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.
22 matches
Mail list logo
