Date: Mon, 24 Sep 2001 12:07:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp-workers AT delorie DOT com
Subject: Re: rm -rf disaster bug [was Re: gcc-3.01 seems unstable]
In-Reply-To: <10109240223.AA03185@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1010924120718.25254F@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 23 Sep 2001, Charles Sandmann wrote:

> The problem only happens when the short name length equivalent (w/o drive) 
> of the directory exceeds 64 characters (even when using lfn functions).

As I wrote elsewhere today, I cannot seem to be able to reproduce this
on Windows 98 SE unless I set LFN=n.

> Wrote a simple test program to chdir to args on command line, printing
> return codes and results from getcwd at each step.  Two args:
> .libs/libstdc++.lax ..

Please post the test program's source, I'd like to run it on a few
system to which I have access.

> So to protect your files, run with the LFN TSR (which prevents you from
> going too deep).

And in general, use GNU and DJGPP software whenever you can ;-)  Yay!

> I'll have to look and see if we can add some protection for this.

It sounds like this protection needs to be Windows-version specific,
since the problems don't happen under LFN on 9X.

Thanks for digging into this.