home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!know!hri.com!noc.near.net!news.Brown.EDU!qt.cs.utexas.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!darwin.sura.net!ra!tantalus!eric
- From: eric@tantalus.dell.com (Eric Youngdale)
- Newsgroups: comp.os.linux
- Subject: Re: Compiler Internel error, help!
- Message-ID: <3590@ra.nrl.navy.mil>
- Date: 13 Sep 92 17:09:36 GMT
- References: <3577@ra.nrl.navy.mil> <716390264snx@kerberos.demon.co.uk>
- Sender: usenet@ra.nrl.navy.mil
- Organization: Naval Research Laboratory
- Lines: 20
-
- In article <716390264snx@kerberos.demon.co.uk> alovell@kerberos.demon.co.uk (Anthony Lovell) writes:
- >
- >In article <3577@ra.nrl.navy.mil> eric@tantalus.dell.com writes:
- >
- >> I am wondering if the new memory manager is setting things up so that
- >>we can no longer write to read-only pages and is more strict about null> pointer
- >>references. Could this explain the sudden rash of segfaults?
- >>
- >Surely thats the whole point about read-only pages ,you're not to write
- >to them
-
- This is true, but the kernel does not enforce this (i.e. you can
- write to a read-only page). At some point in the future, Linus will change
- things over so that this is no longer possible.
-
- -Eric
-
- --
- Eric Youngdale
- eric@tantalus.nrl.navy.mil
-