https://bugs.kde.org/show_bug.cgi?id=451843
--- Comment #6 from Amit <akami...@hotmail.com> --- (In reply to Paul Floyd from comment #5) > What I have so far > > paulf> sudo sysctl kern.elf64.allow_wx=0 > kern.elf64.allow_wx: 1 -> 0 > euler:/usr/home/paulf > paulf> /home/paulf/scratch/valgrind/vg-in-place --help > --6689:0: main Valgrind: FATAL: > --6689:0: main sysctl kern.elf64.allow_wx sysctl is 0. > --6689:0: main Set this sysctl with > --6689:0: main 'sysctl kern.elf64.allow_wx sysctl=1'. > --6689:0: main Or, alternatively, run valgrind with > --6689:0: main 'proccontrol -m wxmap -s enable valgrind [options] > prog-and-args' > --6689:0: main Cannot continue. > > It seems to me that proccontrol -m wxmap is only on FreeBSD 14. > Yes as of now as of now its only in FreeBSD14 , but it seems it might get back ported in upcoming FreeBSD13.1 release > kern.elf64.allow_wx sysctl is in FreeBSD 13, do you know if it is also in > 12.3? kern.elf64.allow_wx sysctl was added in FreeBSD together with W^X feature, so if you are on a FreeBSD release that doesn't have kern.elf64.allow_wx , valgrind should have no issues doing WX map. -- You are receiving this mail because: You are watching all bug changes.
