home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!utcsri!torn!newshub.ccs.yorku.ca!nexus.yorku.ca!wlanders
- From: wlanders@nexus.yorku.ca (W L Anderson)
- Subject: Re: physical memory protection with MMU
- Message-ID: <1992Nov22.164517.21820@newshub.ccs.yorku.ca>
- Sender: news@newshub.ccs.yorku.ca (USENET News System)
- Organization: York University, CS Dept. Toronto
- References: <1eccinINNbv2@darkstar.UCSC.EDU> <1992Nov21.183408.23912@newshub.ccs.yorku.ca> <1en513INNguv@darkstar.UCSC.EDU>
- Date: Sun, 22 Nov 1992 16:45:17 GMT
- Lines: 14
-
- >The drawback is that the message could contain a pointer to some other
- >chunk of memory that isn't declared MEMF_PUBLIC. While Exec could make
- >the message's memory MEMF_PUBLIC if needed, since it doesn't enforce a
- >particular structure upon messages, it wouldn't know that the message
- >contained a pointer and thus couldn't change the type of the second
- >memory block. The process that received the message would then crash
- >when it tried to access that memory.
-
- I guess that would cause a problem :). This sure seems kind of annoying,
- particularly when it back in the ADos 1.0 days that we might eventually have
- memory protection and such. Somehow, there must be way.
-
- Tom Hayko
- wlanders@nexus.yorku.ca
-