Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site bunker.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!ittvax!bunker!reno From: reno@bunker.UUCP (Jim Reno) Newsgroups: net.unix-wizards Subject: Re: vi core dumping on Sun 2 (fixed, but would like explanations) Message-ID: <882@bunker.UUCP> Date: Wed, 26-Jun-85 09:43:14 EDT Article-I.D.: bunker.882 Posted: Wed Jun 26 09:43:14 1985 Date-Received: Sat, 29-Jun-85 02:45:24 EDT References: <168@ittral.UUCP> Organization: Bunker Ramo, Trumbull Ct Lines: 11 Oddly, we recently had a similar problem on a VAX, also with 'vi'. Since the sticky bit is on, a copy of the text is being maintained in the swap area (even when nobody is executing it). Later invocations result in the text being read from the swap area, not the binary file. Hence if the image in swap has a bad block, it will bomb, even if the original binary is still good. (Our situation was caused by a hardware problem in accessing the swap area). Of course, this just changes the problem to 'why did the swap image get corrupted?'