https://bugs.kde.org/show_bug.cgi?id=451843
--- Comment #1 from Paul Floyd <pjfl...@wanadoo.fr> --- There is no make option, I'm fairly certain. I also believe that it really is necessary. Roughly speaking the Valgrind startup process is 1) 'valgrind' runs and execs the tool (e.g., memcheck, which I'll use from here on) 2) memcheck is a standalone exe not linked with any libraries, so it has to bootstrap itself 3) when the guest runs (starting the ld.so to load the guest exe into memory) it will be doing RX mmaps 4) memcheck monitors the mmaping and records the access control As a workaround, don't use "sysctl kern.elf64.allow_wx=0" As a fix, I'll add a check if this is set and print a message saying that you need to turn it on. I already do this with "security.bsd.unprivileged_proc_debug=1". -- You are receiving this mail because: You are watching all bug changes.
