[PATCH] libc_r bug: successful close(2) sets errno to ENOTTY

[Enache Adrian]

On Mon, Nov 24, 2003 a.d., Jacques A. Vidrine wrote:
> The application is broken.  You must only check errno if you get an
> error indication from the library call.

Sorry, but I don't see your point. I know when to check for errno.
If you took the little illustrating program for a real life example of
the use of errno, that's unfortunate :-)

The problem is that the emulated/wrapped close from libc_r does not
behave like the real one. libc_r is leaking some of its guts
(the tricks it's doing with O_NONBLOCK, etc) in the interface.
This is technically a bug. The fix was trivial.

Regards,
Adi