Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 1 Nov 2000 00:52:46 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT sources DOT redhat DOT com
Subject: Re: latest cygwin does not track pwd?
Message-ID: <20001101005246.A6570@redhat.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <14847 DOT 5635 DOT 636000 DOT 348903 AT gargle DOT gargle DOT HOWL> <4 DOT 3 DOT 1 DOT 2 DOT 20001031140921 DOT 02027560 AT pop DOT ma DOT ultranet DOT com> <20001031142519 DOT B28272 AT redhat DOT com> <39FF9C8C DOT 7597BC80 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <39FF9C8C.7597BC80@ece.gatech.edu>; from cwilson@ece.gatech.edu on Tue, Oct 31, 2000 at 11:31:08PM -0500

On Tue, Oct 31, 2000 at 11:31:08PM -0500, Charles Wilson wrote:
>Christopher Faylor wrote:
>cwd =
>
>just as Richard Kim says.  The code for Cwd::cwd on cygwin is
>implemented by <perl-src>/cygwin.c -- but I don't know why it's
>failing.  Patches gratefully accepted (and archived -- I'm not planning
>to release a new perl build myself until 5.6.1 comes out; and probably
>not even then if a third party takes the initiative...

The problem is that it looks like perl is calling getcwd like this:

getcwd (NULL, 0);

and cygwin is returning a NULL, as is mandated by both the Single Unix
Specification and the linux man page.  1.1.4 allowed zero length length
arguments but that was a bug that I fixed in 1.1.5.

I had no idea that people were relying on the bug.

I'm not sure what to do about this.  I am loathe to accomodate a bug
like this but I don't want to force a new perl release or endure to the
next two years of "I cygwined my perl 1.1.[5-9] and it am broke" messages
either.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com