Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 21 Apr 2005 14:44:29 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: findutils still broken Message-ID: <20050421184429.GA1883@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050421182020.GG26356@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Thu, Apr 21, 2005 at 07:24:00PM +0100, Dave Korn wrote: >----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. Yes. I know. Nevertheless, Cygwin does try only to set errno when there is an error. There are some cases where that isn't true but I didn't see any that referred to EISDIR. cgf -- 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/