Pádraig Brady wrote:
> Ah this issue is restricted to glibc's MALLOC_CHECK_ implementation.
Ah, that explains why I got different results than you did.
> I've reported the glibc bug at:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27870
Thanks!
> The attached avoids this part of the test
On 15/05/2021 16:49, Bruno Haible wrote:
Hi Pádraig,
On glibc-2.31-5.fc32.x86_64 I'm seeing this test failure with coreutils,
since the tests are now checking for a specific errno.
I just checked a later Fedora 34 system which has the same issue.
For me, a testdir created through
Hi Pádraig,
> On glibc-2.31-5.fc32.x86_64 I'm seeing this test failure with coreutils,
> since the tests are now checking for a specific errno.
> I just checked a later Fedora 34 system which has the same issue.
For me, a testdir created through
./gnulib-tool --create-testdir
On 5/15/21 9:04 AM, Pádraig Brady wrote:
I'm wondering should we be more relaxed here as,
there is only one standardised ENOMEM error from realloc,
so code doesn't have to behave differently based on what the errno is.
We've already relaxed the errno test for reallocarray, where NetBSD
On glibc-2.31-5.fc32.x86_64 I'm seeing this test failure with coreutils,
since the tests are now checking for a specific errno.
I just checked a later Fedora 34 system which has the same issue.
Specifically test-realloc-gnu is enabled in coreutils
and it's failing as realloc is returning NULL as
