Date: Mon, 14 May 2001 12:31:26 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Martin Stromberg cc: djgpp-workers AT delorie DOT com Subject: Re: Fileutils 4.0 and symlinks In-Reply-To: <200105140748.JAA08651@lws256.lu.erisoft.se> Message-ID: 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 Mon, 14 May 2001, Martin Stromberg wrote: > Richard said: > > that this is the wrong thing to do.) This caused the DOS box to GPF. I had > > to remove '-nostdlib' to prevent a GPF, when configuring. Using > > Lately I've had serious problems with utod. Perhaps related? Not very likely, IMHO, if Richard's hypothesis about not enough file handles is true. > What happens for me is WINDOZE puts up BSOD or just reboot without > warning. The main problem is I've not found any easy way to reproduce > it. If I after the reboot try to run the command again it works fine. > > I run the bleeding edge from CVS, plus Charles' stub correction, my > append fixes and Eli's NT-crash workaround. Ordinary version of the > tools from precompiled .ZIPs except fileutils which is recompiled with > with the latest libc. Note that utod comes from CVS so it's the > bleeding edge. > > This started to appear after the NT-crash workaround but I hadn't had > the need to use utod until recently so I don't particularly suspect > that patch. The W2K-crash patch affects utod only in its exit code. If the reboots are during its exit procedure, after it processed all the files, we can suspect that patch; otherwise, it's unrelated. It might be a good idea to add debugging code to utod which would write to a disk file some progress log. If you use fflush and fsync after each fprintf, it's quite possible that the log file will tell something interesting, even if Windows blows up. > > BTW Mark, bnu210b.mft contains two directories listed - man and man/cat1. > > This is bad if you use 'rm -rf @bnu210b.mft' to uninstall binutils 2.10. > > Isn't the command you should use "rm -f @bnu210b.mft"? Yes, using -r is not recommended, since some zip archives record directories which don't belong to this specific package, like share/ or man/, for example. If you use -r, you will wipe them out (silently!).