On 1/31/19 2:22 PM, Bruce Dubbs wrote:
Will there be a new grep release soon?
I don't have any plans. This bug doesn't seem to be that urgent to fix.
On 01/31/2019 03:34 PM, Paul Eggert wrote:
On 1/25/19 4:24 PM, Paul Eggert wrote:
On 1/22/19 11:08 PM, arn...@skeeve.com wrote:
Do you have an ETA on when the fix will get pushed to GNULIB?
Glibc is scheduled for release on February 1, and I plan to update
glibc and Gnulib soon after it's re
On 1/25/19 4:24 PM, Paul Eggert wrote:
On 1/22/19 11:08 PM, arn...@skeeve.com wrote:
Do you have an ETA on when the fix will get pushed to GNULIB?
Glibc is scheduled for release on February 1, and I plan to update
glibc and Gnulib soon after it's released (which may be a bit later
than Feb.
Paul Eggert wrote:
> On 1/22/19 11:08 PM, arn...@skeeve.com wrote:
> > Do you have an ETA on when the fix will get pushed to GNULIB?
>
> Glibc is scheduled for release on February 1, and I plan to update glibc
> and Gnulib soon after it's released (which may be a bit later than Feb. 1).
Excelle
On 1/22/19 11:08 PM, arn...@skeeve.com wrote:
Do you have an ETA on when the fix will get pushed to GNULIB?
Glibc is scheduled for release on February 1, and I plan to update glibc
and Gnulib soon after it's released (which may be a bit later than Feb. 1).
Paul Eggert wrote:
> On 1/22/19 12:44 AM, arn...@skeeve.com wrote:
> > If I may beg to differ, I see no reason that GNULIB can't be
> > ahead of GLIBC.
> The only reason is avoiding hassle: I'd have to decouple this gnulib
> file from glibc now (which requires changing some other administrative
On 1/22/19 12:44 AM, arn...@skeeve.com wrote:
If I may beg to differ, I see no reason that GNULIB can't be
ahead of GLIBC.
The only reason is avoiding hassle: I'd have to decouple this gnulib
file from glibc now (which requires changing some other administrative
file), and then recouple it late
If I may beg to differ, I see no reason that GNULIB can't be
ahead of GLIBC. In particular for the benefit of programs that use
it, like grep/sed/gawk.
If necessary, I can copy/paste the change from the bug report, but
it'd be nicer if you'd just push it to GNULIB.
Thanks,
Arnold
Paul Eggert w
On Mon, Jan 21, 2019 at 11:32 AM Paul Eggert wrote:
> Thanks for the bug report. I tracked it down to a read buffer overrun in
> glibc's
> regexec.c and filed a bug report with a fix here:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=24114
>
> glibc is frozen right now (it's just before th
Thanks for the bug report. I tracked it down to a read buffer overrun in glibc's
regexec.c and filed a bug report with a fix here:
https://sourceware.org/bugzilla/show_bug.cgi?id=24114
glibc is frozen right now (it's just before the glibc 2.29 release), so most
likely the bug fix will appear i
Hi,
Latest `grep` (git commit 1019e6e) compiled with asan may cause a
heap-buffer-overflow when `-i` is specified.
./grep -i '\(\(\)*.\)*\(\)\(\)\1' /bin/chvt
=
==16206==ERROR: AddressSanitizer: heap-buffer-overflow on addre
11 matches
Mail list logo
