3 ms·
> This is just plain ugly. Yeah. Unfortunately the only really efficient protection mechanisms that modern processors have is virtual memory. C++ programs gene
by titzer 11y ago
> This is just plain ugly.
Yeah. Unfortunately the only really efficient protection mechanisms that modern processors have is virtual memory. C++ programs generally unmap the first few pages for exactly the same reason; to catch nullptr derefs.
> Why should the normal operation of a program written in a high-level language trigger page faults?
NullPointerExceptions are not considered normal operation. They are safety violations that have a controlled, well-defined semantics. BTW page faults happen all the time; the OS transparently handles them and maps in new pages as necessary. The problem you are referring occurs when a page fault happens and the OS knows there is no mapping for those addresses.
> How do you guarantee that the OS won't give you back the same pages you unmapped
Because the mapping is for an address space range (e.g. 0-N), and the OS does not overlap new request with existing mappings unless specified in the request.
- catnaroek 11y ago> and the OS does not overlap new request with existing mappings unless specified in the request. Ah, so by “unmap”, you actually something like POSIX's `mprotect()`, rather than `munmap()`?
- titzer 11y agoSorry, yes. You can do this just through segment declarations in both ELF and MachO binary formats, to prevent anything getting accidentally mapped there before startup.
- catnaroek 11y ago> NullPointerExceptions are not considered normal operation. They are safety violations that have a controlled, well-defined semantics. I'm not really buying this. My definition of “normal operation” is very simple: Everything but FFI calls. Normal operation in a safe language is supposed to be safe.