home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!caen!hellgate.utah.edu!cc.usu.edu!ivie
- From: ivie@cc.usu.edu (CP/M lives!)
- Newsgroups: comp.arch
- Subject: Re: PALcode instructions vs TRAP instructions
- Message-ID: <1992Aug17.101735.58202@cc.usu.edu>
- Date: 17 Aug 92 10:17:35 MDT
- References: <1992Aug12.092211.58077@cc.usu.edu> <34303@cbmvax.commodore.com> <1992Aug16.195833.58188@cc.usu.edu> <Bt4Grs.2Ap@exnet.co.uk>
- Organization: Utah State University
- Lines: 18
-
- In article <Bt4Grs.2Ap@exnet.co.uk>, dhd@exnet.co.uk (Damon) writes:
- > In article <1992Aug16.195833.58188@cc.usu.edu> ivie@cc.usu.edu (CP/M lives!) writes:
- >>
- >>The problem with wild pointers should be solved as soon as the OS is up far
- >>enough to initialize the page tables. If the page tables don't include the
- >>console memory, the OS can't get at them.
- >
- > Mmm. But waht about bugs (eg wild pointers) in the OS? I mean, am I missing
- > something, or don't OSes still have bugs in them? B^>/2
-
- Yes, but on a VAX or (possibly) an Alpha, the opportunity for a bug to
- happen that corrupts the console data is small and limited to the
- bootstrap. Yes, you can have wild pointers in the OS, but unless it's in
- the bootstrap it's not going to corrupt the memory reserved for the
- console and PALcode.
-
- Roger Ivie
- ivie@cc.usu.edu
-