🚀 go-pugleaf

In article <1991Nov12.010835.16161@newshost.anu.edu.au> goomcb32@vulcan.anu.edu.au (Miles Goodhew) writes:
>In propaganda <1991Nov11.185046.6524@CSD-NewsHost.Stanford.EDU>, comrade amorgan@Neon.Stanford.EDU (Crunchy Frog) rambles:
>>Does AmigaDos 2.0 have memory protection such that writing outside of
>>malloc'ed mem will cause a seg fault (or whatever) rather than a reboot?
>>To my mind, that is one of the major pains of developing on non-Unix
>>(or rather MSDOS, Mac OS, AmigaDos, etc) operating systems.
>
>There's a program called "enforcer", which utilises an mmu if you have one. I
>don't have an MMU, so I don't know a great deal about its operation. I
>believe that it doesn't just extinguish processes as in unix (it probably will
>let you though), it detects read and write hits outside a processes segment,
>etc.
>
>MHG.
>
As far as I know, enforcer will only catch accesses to some forbidden
addresses; it won't give you any kind of memory-protection. AmigaOS2.0
won't give you any protection; it is still designed to run on a 68000-
system and therefore it doesn't use the MMU. If one program crashes,
you still have to reboot, because nobody knows what the tasks did before
the OS stopped it. Every task has access to all resources at all times.

       Christian

Sorry, no email at the moment.