Bug 17956 – core.memory unittest failure (possibly glibc 2.26 specific)

Unittester started failing locally, the only change is that I upgraded to the newest Ubuntu OS release. Which bumped the glibc version from 2.24 to 2.26. --- │ void* z = pureMalloc(size_t.max - 2); // won't affect `errno` │ assert(errno == fakePureGetErrno()); // errno shouldn't change ├───> assert(z is null); --- I've raised a bug against glibc (https://sourceware.org/bugzilla/show_bug.cgi?id=22375) However this test should be fixed, pureMalloc(long.max-2) maybe?

Someone from glibc maintainers added a security flag to the upstream bug report. This seems to be at least an acknowledgement that its an external problem.

I can reproduce this on my machine with glibc 2.26-8 :/

> However this test should be fixed, pureMalloc(long.max-2) maybe? Let's see what the auto-tester says: https://github.com/dlang/druntime/pull/1991

Commits pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/52d7e9475ab40a61054e79a1a7cec46d02bb1c81 Fix Issue 17956 - core.memory unittest failure (possibly glibc 2.26 specific) https://github.com/dlang/druntime/commit/ff04e96da53da68b795496879382bf7bd4f74694 Merge pull request #1991 from wilzbach/fix-17956 Fix Issue 17956 - core.memory unittest failure (possibly glibc 2.26 s… merged-on-behalf-of: Petar Kirov <[email protected]>

Commits pushed to stable at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/52d7e9475ab40a61054e79a1a7cec46d02bb1c81 Fix Issue 17956 - core.memory unittest failure (possibly glibc 2.26 specific) https://github.com/dlang/druntime/commit/ff04e96da53da68b795496879382bf7bd4f74694 Merge pull request #1991 from wilzbach/fix-17956