X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10201152300.AA20792@clio.rice.edu> Subject: ls weirdness on root drive To: acottrel AT ihug DOT com DOT au (Andrew Cottrell) Date: Tue, 15 Jan 2002 17:00:52 -0600 (CST) Cc: djgpp-workers AT delorie DOT com (DJGPP developers) In-Reply-To: <008201c19d9f$0b6f50d0$0102a8c0@acceleron> from "Andrew Cottrell" at Jan 15, 2002 07:31:04 PM X-Mailer: ELM [version 2.5 PL2] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Windows 2000, using both ls.exe from v2.03 refresh and v2.04 most recent I don't see a problem on my CD drive, but I *DO* SEE A PROBLEM on the root directory of my C drive. The directory stops after autoexec.bat. Setting lfn=n and it shows all files. "." shows an error with lfn active under 2.04 but no error under 2.03, and no error on the same exe with lfn=n on 2.04. ls shows only autoexec.bat (a hidden file) ls -l shows only the directories (OK since all other files hidden/system?) ls -la shows only . .. and autoexec.bat So it appears that findfirst gets really confused on attributes with lfn on Win2k. The first file with the system bit set (boot.ini) seems to stop it from going further. But doing -l doesn't (extra findfirst in stat makes it behave?) I guess we haven't done much testing on directories with system bits set. I know it didn't work properly for finding labels. I don't see problem on XP. (somthing they fixed?) By the way, the env crash appears when it is doing a loop on the 3rd argument in the main(*) arg list, putenv()'ing all of those strings. Putenv calls free(environ) which is where it crashes (inside free). I don't see any changes which would cause/fix this, so it's probably still lurking. I don't know why setting DJGPP would prevent the problem, or why running in a debugger prevents the problem. Sigh.