Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!odi!ed
From: ed@odi.com (Ed Schwalenberg)
Newsgroups: comp.windows.ms.programmer
Subject: Re: UAE's - how are they detected
Message-ID: <1991May29.164121.27600@odi.com>
Date: 29 May 91 16:41:21 GMT
Article-I.D.: odi.1991May29.164121.27600
References: <1991May25.054957.1151@mnemosyne.cs.du.edu> <1991May28.173139.8139@hyper.hyper.com>
Organization: Object Design, Inc.
Lines: 19
In-Reply-To: bonneau@hyper.hyper.com's message of Tue, 28 May 1991 17:31:39 GMT

In article <1991May28.173139.8139@hyper.hyper.com> bonneau@hyper.hyper.com (Paul Bonneau) writes:
  Only thos writes outside the bounds of a selector can be
  detected.  Once we have win32 (now called Windows 4
  apparently) where an application will have a virtual address
  space of several gigabytes, wild writes will be much harder
  to detect.  One of the (few) benefits of the 386's segmented
  architecture is that it *does* make memory trashing easier
  to find.

It is possible to use the page-protection features of the 386
architecture to implement much finer-grained memory protection,
both between applications and within a single application.  This
will let the programmer have the best of both worlds: a uniform
address space and a high degree of protection against misbehaved
programs.

Whether the developers of future PC systems like Win32 or OS2 3.0
actually take advantage of the power of the chip architecture
remains to be seen.