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: Problem with sh/bash and snapshot cygwin1-20050825.dll Date: Fri, 26 Aug 2005 15:51:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050826144755.GF12490@trixie.casa.cgf.cx> Message-ID: ----Original Message---- >From: Christopher Faylor >Sent: 26 August 2005 15:48 > On Fri, Aug 26, 2005 at 06:17:13AM -0600, Eric Blake wrote: >> While you're at it, fix realpath(NULL, buf) to set buf[0]='\0', instead >> of leaving garbage there. > > What's the rationale for touching buf when realpath is returning an error > and setting EINVAL? > > cgf Standards-mandated leeway? http://www.opengroup.org/onlinepubs/009695399/functions/realpath.html Upon successful completion, [ ... ]. Otherwise, realpath() shall return a null pointer and set errno to indicate the error, and the contents of the buffer pointed to by resolved_name are undefined. 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/