Re: test-strerror_r fails on GNU/Hurd

2022-01-03 Thread Bernhard Voelker
On 1/3/22 02:52, Paul Eggert wrote: > On 1/2/22 16:28, Bernhard Voelker wrote: >> 1073741858: that's 2^30 +34 > > Could it be an address, or part of an address, that is incorrectly > treated as an integer? A mistake like that is quite plausible given the > "does it return char * or int?" API of

Re: test-strerror_r fails on GNU/Hurd

2022-01-02 Thread Paul Eggert
On 1/2/22 16:28, Bernhard Voelker wrote: 1073741858: that's 2^30 +34 Could it be an address, or part of an address, that is incorrectly treated as an integer? A mistake like that is quite plausible given the "does it return char * or int?" API of strerror_r.

Re: test-strerror_r fails on GNU/Hurd

2022-01-02 Thread Bernhard Voelker
On 1/2/22 21:46, Bruno Haible wrote: > Bernhard Voelker wrote: >> The error in the test-suite.log shows: >> >> FAIL: test-strerror_r >> = >> >> test-strerror_r.c:112: assertion 'ret == ERANGE || ret == EINVAL' failed >> FAIL test-strerror_r (exit status: 134) >> > > I s

Re: test-strerror_r fails on GNU/Hurd

2022-01-02 Thread Bruno Haible
Bernhard Voelker wrote: > The error in the test-suite.log shows: > > FAIL: test-strerror_r > = > > test-strerror_r.c:112: assertion 'ret == ERANGE || ret == EINVAL' failed > FAIL test-strerror_r (exit status: 134) > I see this same test failure also on older glibc/Li