Date: Sun, 24 Jul 2022 21:30:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262378] emulators/wine-devel won't start on CURRENT due to ASLR changes Message-ID: <bug-262378-227-KOz6a2Bc6t@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262378-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262378-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262378 Stefan E=C3=9Fer <se@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |FIXED --- Comment #14 from Stefan E=C3=9Fer <se@FreeBSD.org> --- (In reply to Alexander Vereeken from comment #13) Thank you for reminding me that there are other Wine ports that have the sa= me rum-time issue with ASLR: I have applied the same elfctl -noalsr fixup to the binaries created by the emulators/wine and emulators/wine-proton ports. Disabling ASLR on the Wine binaries is only a work-around, but the correct = fix is much more complex and requires a new function to be implemented to provi= de suitable mapping addresses to be used by Wine when it allocates memory. I have looked at the code that has been implemented to solve this issue on macOS, and it is not directly applicable to FreeBSD - therefore selectively exempting the Wine binaries from ASLR is the much quicker solution to a pressing problem ... I'll close this PR, since the issue has been dealt with (admittedly in a=20 sub-optimal way, but the macOS patch mentioned in comment 12 does the same thing in a slightly different way). If you think that disabling ASLR is not good enough, then feel free to open= a feature request PR for the missing functionality that would allow ASLR to be enabled for Wine on FreeBSD. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262378-227-KOz6a2Bc6t>