Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!apple!well!oster
From: oster@well.sf.ca.us (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: A use for protected mode after all
Message-ID: <21919@well.sf.ca.us>
Date: 2 Dec 90 16:39:10 GMT
References: <2382.2754d79e@waikato.ac.nz> <1990Nov29.025924.7662@maverick.ksu.ksu.edu> <4857@husc6.harvard.edu>
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 15

In article <4857@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
>I believe that software that doesn't crash in the first place is the best
>way to go

Here! Here! and that is why the debugger should grab the MMU and protect
itself: it is precisely while you are debugging software that you are working
with buggy software. Once software is debugged it isn't buggy. Rich is right,
it is much easier job for a debugger to protect itself than it is for the
Mac O.S. to protect every program from every other, and itself, and still allow
legitimate access, since legitimate access is so unstructured. It would be
nice, but I'd rather have the easy part early than the nice one, when it 
happens to get finished.
-- 
-- David Phillip Oster - At least the government doesn't make death worse.
-- oster@well.sf.ca.us = {backbone}!well!oster