Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!pyramid!pesnta!amd!amdcad!lll-crg!lll-lcc!unisoft!paul
From: paul@unisoft.UUCP
Newsgroups: net.arch
Subject: Re: oops, corrupted memory again!
Message-ID: <57@unisoft.UUCP>
Date: Mon, 5-May-86 11:52:25 EDT
Article-I.D.: unisoft.57
Posted: Mon May  5 11:52:25 1986
Date-Received: Wed, 7-May-86 06:19:30 EDT
References: <117@prairie.UUCP> <780@bentley.UUCP> <231@ubc-cs.UUCP>
Reply-To: paul@unisoft.UUCP (Paul Campbell)
Organization: UniSoft Systems; Berkeley, CA
Lines: 14

<oog>

	I too spent many happy years working on a system that ALWAYS verified
pointers and array bounds ... Burroughs large systems (B6700 et al), they
have such a crude memory management (to be fair they were designed in the late
60s early 70s, and have a stack architecture) that the system integrity depends
on the fact the NOONE can make machine code with out using a special trusted
program called a "compiler" (ie only a "compiler" can set a file's type to
code file). It takes the super-user to mark a code file as being a "compiler"
code file. Needless to say no-body really misses not being able to turn off
range checking, except for the Fortran types who get programs from elsewhere ...

		Paul Campbell
		..!ucbvax!unisoft!paul