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: <10201160458.AA18094@clio.rice.edu> Subject: Re: ls weirdness on root drive To: djgpp-workers AT delorie DOT com Date: Tue, 15 Jan 2002 22:58:54 -0600 (CST) Cc: acottrel AT ihug DOT com DOT au (Andrew Cottrell) In-Reply-To: <10201152300.AA20792@clio.rice.edu> from "Charles Sandmann" at Jan 15, 2002 05:00:52 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 > "." 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. Fixed this one (lstat.c). I introduced it when doing relative paths - didn't know the the fixpath'ed string could have both forward and backward slashes. ls behavior on my home W2K system refuses to show any strangeness on any drives. So far only the C drive one one W2K system at work, and only in the root directory, shows bad behavior. the env crash is scary. At crash it's showing using around 6Mb of memory with the stack at the 5.5Mb mark. Run under the debugger The stack is at 0.7Mb area. The crash register values change if run under go32-v2. It seems to be some uninitialized memory problem? I don't see how the stack location could change that much unless there was a bug in sbrk() ... If I set the djgpp environment variable to point to a file, if I make that file small it will still crash; if it is larger it then runs. (This hint was sent to me by an OpenGUI tester). We get the size of the DJGPP.ENV file and malloc that, read the file there. Does that pepper the memory with something that prevents a problem? I was also told adding a malloc(1) early in main also prevents the OpenGUI problems.