delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/11/01/11:08:50

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
From: takashi AT flab DOT fujitsu DOT co DOT jp
Date: Wed, 01 Nov 2000 23:58:39 +0900
Message-ID: <87k8anbuxt.wl@EDEN.people.flab.fujitsu.co.jp>
To: cygwin AT sources DOT redhat DOT com
Subject: Re: latest cygwin does not track pwd?
In-Reply-To: In your message of "Wed, 1 Nov 2000 00:52:46 -0500"
<20001101005246 DOT A6570 AT 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>
<20001101005246 DOT A6570 AT redhat DOT com>
User-Agent: Wanderlust/1.1.1 (Purple Rain) WEMI/1.13.7 (Shimada) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.2 (beta36) (Notus) (i586-pc-cygwin)
MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada")

Hi. Chris,

I found the latest inetutils-1.3.2-7 has the same behaviour.

$ ftp localhost
   .......
ftp> pwd
550 Invalid argument.

inetutils-1.3.2/ftpd/ftpd.c also relys on this bug.

$ grep getpwd ftpd.c
        path = getcwd (0, 0);
                char *cwd = getcwd (0, 0);
        char *path = getcwd (0, 0);

The ftpd should be fixed, I think.

Regards,
Takashi Nishigaya

> 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
> 

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019