Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!prls!pyramid!hplabs!felix!toby
From: toby@felix.UUCP (Toby Gottfried)
Newsgroups: net.lang.c,net.lang.c++
Subject: Re: oops, corrupted memory again!
Message-ID: <1138@felix.UUCP>
Date: Mon, 5-May-86 16:09:25 EDT
Article-I.D.: felix.1138
Posted: Mon May  5 16:09:25 1986
Date-Received: Thu, 8-May-86 20:45:26 EDT
References: <4495@cbrma.UUCP> <763@bentley.UUCP> <7232@tekecs.UUCP>
Reply-To: toby@felix.UUCP (Toby Gottfried)
Organization: FileNet Corp., Costa Mesa, CA
Lines: 22
Xref: linus net.lang.c:8183 net.lang.c++:167

In article <763@bentley.UUCP> kwh@bentley.UUCP (KW Heuer) writes:
>Now, if only somebody would invent an architecture where all objects,
>including dynamicly allocated objects, are isolated in memory, then any
>subscript error would cause an immediate memory fault.  

	Burroughs did exactly this in their Large Systems
	over 20 years ago.

>You'd still be vulnerable to completely wild pointers (but less likely 
>in a huge address space), 

	Not a problem - the address space isn't flat.

>and overflow of an array inside a structure might be untrappable,
>but otherwise it sounds like a great machine to do your debugging on.

	It is.

-- 
Toby Gottfried
 FileNet Corp	 {ucbvax,ihnp4,decvax}!trwrb!felix!toby
Costa Mesa, CA