home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!wupost!psuvax1!psuvm!dxb132
- Organization: Penn State University
- Date: Thu, 19 Nov 1992 18:21:06 EST
- From: <DXB132@psuvm.psu.edu>
- Message-ID: <92324.182106DXB132@psuvm.psu.edu>
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: Why doesn't Amiga core-dump? *sigh*
- References: <92323.003545BGT101@psuvm.psu.edu>
- <1992Nov18.133139.21744@ifi.unizh.ch> <92323.182614BGT101@psuvm.psu.edu>
- <1992Nov19.084052.12588@ifi.unizh.ch> <92324.155004BGT101@psuvm.psu.edu>
- Lines: 20
-
- In article <92324.155004BGT101@psuvm.psu.edu>, Blaise Tarr
- <BGT101@psuvm.psu.edu> says:
-
- >In article <1992Nov19.084052.12588@ifi.unizh.ch>, (Matija Milostnik) says:
- >>
- >>In the message you could have a pointer to any memory
- >>location you own. This situation CANT be protected, cause the system doesnt
- >>know about it.
-
- >That's where you would use the MEMF_PUBLIC flag. Quoting from the RKRM:
- >"This indicates that the memory should be accessible to other tasks."
- >Therefore, all correctly written programs use this flag if they want other
- >programs to use their memory area.
-
- This is an unsafe assumption at best. Besides, the programmer doesn't
- really know what tasks, if any, might need to share data when doing
- I/O. (Usually at least two...the filesystem and device driver). It's
- not strictly defined, and may change in the future.
-
-
-