On 5/1/22 13:28, Bruno Haible wrote:
I would argue that glibc should use a different errno value in this case.
Either errno value makes sense to me. If you keep doing a non-blocking
read on a pipe that only you can write to you'll keep getting EAGAIN,
which has the same feel as a bug where yo
Paul Eggert wrote:
> malloc can fail with EAGAIN
> on GNU/Linux and I assume other errno values are also possible.
Indeed [1], although the glibc manual [2] and the Linux man page [3]
don't mention it.
The meaning of EAGAIN in this case is as documented for the mmap()
system call [4]:
"too muc
