> Totally awesome! > > awesome(38099): mmap W^X violation > > It happens once on startup.
No, that is incorrect. It probably happens throughout the program's runtime. mmap/mprotect failures are rate limited and only printed once per process. > Grepping for the obvious stuff doesn't show me the issue, perhaps > it's a library. There is no obvious ill effect from the mmap > failure. > As an aside, iridium runs into mmap W^X all the time, but seems to work fine? iridium (like chrome) is multiple processes. It prints it once per process. > I thought people were getting broken tabs in chrome? There's no obvious ill > effect in iridium from the mmap failure. By default, W^X issues are only reported. To see real action, # sysctl kern.wxabort=1
