Samuel Thibault wrote: > That's already fixed: > > https://patchwork.sourceware.org/project/glibc/patch/20220827134844.1263243-2-samuel.thiba...@ens-lyon.org/ > "Spotted by the libunistring testsuite test-perror2"
Yes, this was exactly the test case that I investigated as well. > https://salsa.debian.org/glibc-team/glibc/-/commit/86b00092f9296be2b212891ed94945d05503b92d Here, the patch "Spotted by the libunistring testsuite test-strerror_r" is not necessary. The test failure was caused by a bug in gnulib, fixed today [1]. The gnulib code made the assumption that strerror_r always returns a thread-safe untruncated string. This assumption is wrong both on glibc/Linux and on glibc/Hurd. Bruno [1] https://lists.gnu.org/archive/html/bug-gnulib/2022-09/msg00007.html
