[Bug 255964] net-p2p/transmission-remote-gui: fails to start when W^X protection is activated

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue May 18 05:45:25 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255964

            Bug ID: 255964
           Summary: net-p2p/transmission-remote-gui: fails to start when
                    W^X protection is activated
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: acm at FreeBSD.org
          Reporter: alster at vinterdalen.se
             Flags: maintainer-feedback?(acm at FreeBSD.org)
          Assignee: acm at FreeBSD.org

In FreeBSD 13.0 release appeared new memory protection mechanism: W^X (write
XOR execute) [0]. But unfortunately, some ports are still not adapted their
code to be able to run in this mode. One of them is
net-p2p/transmission-remote-gui, written in pascal language.

% transgui
exec_new_vmspace: mapping stack size 0x20000000 prot 0x7 failed mach error 2
errno 13
Abort

Workaround [1] with setting `elfctl -e +wxneeded` didn't help either.

Also wonder, what could possibly make this port incompatible with W^X?
Whether FreePascal does have some custom runtime routines that triggers it?
I thought it could be seen only with languages with JIT runtimes, like Java…


[0] https://cgit.freebsd.org/src/commit/?id=2e1c94aa1fd5
[1] https://forums.freebsd.org/threads/rclone-not-working-with-w-x.80279/

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list