Date: Thu, 15 Jun 2023 07:03:35 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 271081] www/firefox: crashes on arm64 with ASLR enabled Message-ID: <bug-271081-21738-jHqDO8Oe2v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271081-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-271081-21738@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=3D271081 Nuno Teixeira <eduardo@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 683 | |18 --- Comment #1 from Nuno Teixeira <eduardo@FreeBSD.org> --- (In reply to Mark Johnston from comment #0) Hello Mark, I'm testing firefox-114.0.1 on 13-STABLE with: $ proccontrol -m aslr -s disable firefox and it runs fine without problems. Recent discussion on: https://lists.freebsd.org/archives/dev-commits-ports-all/2023-June/067113.h= tml What should be done here? - Disable aslr at build time via an option - Show message at install time about disabling aslr at runtime with proccontrol, for aarch64 and let user use it if he having problems - Fix it upstream, optimal solution :) I'm new to aarch64 and I did found some dificulties to get into aslr connection. I remember that some users at forums having same problem with no answer at = all. Thanks --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271081-21738-jHqDO8Oe2v>