>When something explodes in kernel space on Windows, it cannot trap or handle >exceptions by virtue of the processor mode it's in. AmigaOS has the same >difficulty on the MC680x0. It's not like it's restricted to Intel procs. This >is a blue screen, or certain classes of Guru (although not related to memory >protection, causing an exception while in supervisor mode is deadly..), or a >kernel panic, and cannot be avoided. And it happens on all operating systems.
Normal programs shouldn't be able to run in kernel space. And it should be able to recover from a badly written program. That's the purpose of memory protection that normal users are interested in. How did you mean that you can write a BSD program that craches the kernel without exploiting a kernel bug? / John
