[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/2] regex: test for buffer overrun
From: |
Paul Eggert |
Subject: |
Re: [PATCH 2/2] regex: test for buffer overrun |
Date: |
Wed, 10 Apr 2013 22:07:09 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 |
On 04/10/2013 09:48 PM, Dmitry V. Levin wrote:
> I think gnulib's tests/test-regex.c should allow glibc's re_search()
> behavior so that various utilities built --without-included-regex
> wouldn't be penalized by test-regex:
This looks like a good idea, thanks; but shouldn't gnulib/m4/regex.m4
have a similar change?
Even with the change, utilities built --without-included-regex will
still report errors with an unpatched glibc because the tests will
dump core, but I assume that's the intent and that's fine.
- Re: [PATCH 2/2] regex: test for buffer overrun, Nix, 2013/04/01
- Re: [PATCH 2/2] regex: test for buffer overrun, Carlos O'Donell, 2013/04/09
- Re: [PATCH 2/2] regex: test for buffer overrun, Dmitry V. Levin, 2013/04/11
- Re: [PATCH 2/2] regex: test for buffer overrun,
Paul Eggert <=
- Re: [PATCH 2/2] regex: test for buffer overrun, Dmitry V. Levin, 2013/04/11
- [PATCH] regex-tests, regex: allow glibc re_search behavior, Dmitry V. Levin, 2013/04/11
- Re: [PATCH] regex-tests, regex: allow glibc re_search behavior, Paul Eggert, 2013/04/11
- Re: [PATCH] regex-tests, regex: allow glibc re_search behavior, Dmitry V. Levin, 2013/04/11