Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: findutils still broken Date: Thu, 21 Apr 2005 19:24:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-reply-to: <20050421182020.GG26356@trixie.casa.cgf.cx> Message-ID: X-OriginalArrivalTime: 21 Apr 2005 18:24:05.0747 (UTC) FILETIME=[4D1DCC30:01C5469F] ----Original Message---- >From: Christopher Faylor >Sent: 21 April 2005 19:20 > On Thu, Apr 21, 2005 at 05:39:57PM +0000, Eric Blake wrote: >> Also, I've noticed that some cygwin syscalls are sloppy, and change >> errno to EISDIR even when they are successful. > > Cygwin does try only to set errno when there is an error. If you have > specific evidence to the contrary please report it. In any case, it's legitimate to set errno to anything you like in a system call, because the application is only allowed to pay attention to the value of errno if the system call returns an error exception. If the system call returns success (generally zero), the value of errno is undefined and it's not valid to pay any attention to it. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/