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 From: ericblake@comcast.net (Eric Blake) To: cygwin@cygwin.com Cc: Christopher Faylor Subject: Re: Problem with sh/bash and snapshot cygwin1-20050825.dll Date: Fri, 26 Aug 2005 14:56:46 +0000 Message-Id: <082620051456.7539.430F2DAE0006648800001D7322007613940A050E040D0C079D0A@comcast.net> X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0 > 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? Because POSIX states that buf is indeterminate on error, and because Corrina's patch caused a regression (ie. 1.5.18 was setting buf[0] to 0 on error). QofI states that we might as well make the indeterminate buffer useful, in case a user forgets to check the return value being NULL. -- Eric Blake -- 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/