From:	barrett AT cs DOT umass DOT edu ("Daniel J. Barrett")
Subject:	bash "cd" bug when pathname has 3+ periods
9 Jul 1997 17:40:40 -0700 :
Sender:	mail AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199707092136.RAA13822.cygnus.gnu-win32@mail.thecia.net>
Reply-To:	barrett AT cs DOT umass DOT edu
Original-To:	gnu-win32 AT cygnus DOT com
Original-cc:	barrett AT cs DOT umass DOT edu
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

	In Bash 1.14.7(2) under Windows 95, the Bash command "cd"
exhibits incorrect behavior.  This bug does not occur in bash compiled
for UNIX.

	Run "cd" with a pathname that does not exist, and whose last
component is 3 or more periods.  Here are some examples:

	cd ...
	cd /....
	cd /foo/bar/.....

Bash will "cd" into the nonexistent directory.  For example:

        $ pwd
        /
        $ cd ...
        $ pwd
        /...

I did not compile this bash -- I downloaded the binary from ftp.cygnus.com
today as part of USERTOOLS.EXE.

--
Dan Barrett
barrett AT cs DOT umass DOT edu

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -