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

M. Warner Losh imp at bsdimp.com
Mon Nov 24 14:34:31 PST 2003


In message: <20031124182322.GB621 at wombat.fafoe.narf.at>
            Stefan Farfeleder <stefan at fafoe.narf.at> writes:
: On Mon, Nov 24, 2003 at 07:05:02PM +0100, boyd, rounin wrote:
: > From: "Jacques A. Vidrine" <nectar at FreeBSD.org>
: > > The application is broken.  You must only check errno if you get an
: > > error indication from the library call.
: > 
: > errno is only meaningful after a syscall error.
: 
: Wrong, counter-example: strtol().

errno is meaningful for syscalls after an error (the original
message).  The fact that other functions also dink with errno is not
relevant to that statement.

Warner


More information about the freebsd-current mailing list