https://bugs.kde.org/show_bug.cgi?id=451843
--- Comment #2 from Amit <akami...@hotmail.com> ---
(In reply to Paul Floyd from comment #1)
> 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
RX mapping should not be issues , or do you mean WX/RWX mapping ?
> 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".
as a work around you can also use proccontrol ("proccontrol -m wxmap -s enable
valgrind") to let valgrind do WX map, which personally I think is much secure
https://www.freebsd.org/cgi/man.cgi?query=proccontrol&apropos=0&sektion=1&manpath=FreeBSD+14.0-current&arch=default&format=html
--
You are receiving this mail because:
You are watching all bug changes.
