Hi, The flag basically means that memory traps don't get forwarded to the application. So the kernel still gets to handle the trap, but the app won't segfault if you access a bad address.
The option is basically to allow the compiler to use speculative memory accesses. Regards, Darryl. On 3/28/2010 2:42 PM, ????? ???????????? wrote: > Does -xsafe=mem work with mmap() for files? From the documentation it > says that -xsafe=mem turns of the memory traps. Does that include > traps used by the kernel to serve files mapped into mmap() into the > process address space? > > Olga
