From owner-freebsd-current@FreeBSD.ORG Tue Nov 25 02:05:41 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E752616A4CE for ; Tue, 25 Nov 2003 02:05:41 -0800 (PST) Received: from smtp.noos.fr (nan-smtp-17.noos.net [212.198.2.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4071A43F75 for ; Tue, 25 Nov 2003 02:05:40 -0800 (PST) (envelope-from boyd@insultant.net) Received: (qmail 22045 invoked by uid 0); 25 Nov 2003 10:05:36 -0000 Received: from unknown (HELO coma) ([81.64.132.185]) (envelope-sender ) by 212.198.2.117 (qmail-ldap-1.03) with SMTP for ; 25 Nov 2003 10:05:36 -0000 Message-ID: <004b01c3b33b$873a67a0$b9844051@insultant.net> From: "boyd, rounin" To: References: <20031124174457.GB27782@madman.celabo.org><03a601c3b2b5$7bc15b80$b9844051@insultant.net><20031124182322.GB621@wombat.fafoe.narf.at><20031124.153349.13027396.imp@bsdimp.com> <20031124230004.GB585@wombat.fafoe.narf.at> Date: Tue, 25 Nov 2003 11:04:30 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Re: [PATCH] libc_r bug: successful close(2) sets errno to ENOTTY X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 10:05:42 -0000 From: "Stefan Farfeleder" > > 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. > > I read boyd's statement as a contradiction to Jacques' one (only after > syscall error vs. after library call error). some libc functions do mangle errno, but only after an error. in my terse statement the intention was to affirm that errno is meaningless unless an error has ocurred (a syscall being the simplest case, while random other libc calls may behave in the same way).