This is the mail archive of the glibc-bugs-regex@sourceware.org mailing list for the glibc project.
Indexes: [Date Index] [Subject Index] [Author Index] [Thread Index] Site Nav: [Browse other archives for this mailing list]
[Browse other mailing lists at this site]
March 21, 2019
08:26 | [Bug regex/24269] regexec: Infinite recursion in check_dst_limits_calc_pos_1 | schwab at linux-m68k dot org |
March 17, 2019
08:44 | [Bug regex/24114] regexec buffer read overrun in "grep -i '\(\(\)*.\)*\(\)\(\)\1'" | cvs-commit at gcc dot gnu.org |
March 16, 2019
22:32 | [Bug regex/24114] regexec buffer read overrun in "grep -i '\(\(\)*.\)*\(\)\(\)\1'" | cvs-commit at gcc dot gnu.org |
22:25 | [Bug regex/24114] regexec buffer read overrun in "grep -i '\(\(\)*.\)*\(\)\(\)\1'" | cvs-commit at gcc dot gnu.org |
March 13, 2019
06:30 | [Bug regex/23393] Handle [a-z] and [A-Z] in consistent portable fashion regardless of locale. | petersen at redhat dot com |
March 09, 2019
10:48 | [Bug regex/24316] regexec() violates POSIX longest match rule | skvadrik at gmail dot com |
00:32 | [Bug regex/24316] regexec() violates POSIX longest match rule | skvadrik at gmail dot com |
00:32 | [Bug regex/24316] New: regexec() violates POSIX longest match rule | skvadrik at gmail dot com |
March 05, 2019
10:46 | [Bug regex/18986] ERE '0|()0|\1|0' causes regexec undefined behavior | schwab at linux-m68k dot org |
10:33 | [Bug regex/24114] regexec buffer read overrun in "grep -i '\(\(\)*.\)*\(\)\(\)\1'" | schwab at linux-m68k dot org |
10:29 | [Bug regex/24269] regexec: Infinite recursion in check_dst_limits_calc_pos_1 | schwab at linux-m68k dot org |
March 01, 2019
10:39 | [Bug regex/18986] ERE '0|()0|\1|0' causes regexec undefined behavior | fweimer at redhat dot com |
02:28 | [Bug regex/18986] ERE '0|()0|\1|0' causes regexec undefined behavior | vapier at gentoo dot org |
Indexes: [Date Index] [Subject Index] [Author Index] [Thread Index] Site Nav: [Browse other archives for this mailing list]
[Browse other mailing lists at this site]