Date: Sat, 02 Apr 2016 07:51:41 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: [Bug 153243] [ibcs2] Seg fault whne running COFF binary using iBCS2 in 8.1 Message-ID: <bug-153243-4077-Fq8rhhXfPH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-153243-4077@https.bugs.freebsd.org/bugzilla/> References: <bug-153243-4077@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153243 Kristoffer Eriksson <ske-89@pkmab.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ske-89@pkmab.se --- Comment #2 from Kristoffer Eriksson <ske-89@pkmab.se> --- This sounds to me like the same problem that was later solved in the following discussion in 2013: https://lists.freebsd.org/pipermail/freebsd-hackers/2013-October/043615.html The solution was to run "sysctl security.bsd.map_at_zero=1” or add “security.bsd.map_at_zero=1“ to /etc/sysctl.conf. The problem was that COFF files want to load at address 0, which is no longer allowed by default. The executable code ends up on the wrong address, and crashes. So it is not really a bug, just difficult to use. There was some follow-up discussion that this setting is documented in aout(4), but that some more documentation and clearer messages might be added for COFF (or iBCS2) too. Or make the COFF loader allow this automatically. Most people would probably never find this out for themselves, and would just conclude that iBCS2 is broken, so I think some of those suggestions should be undertaken. It took me a long time to find this by googling too. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-153243-4077-Fq8rhhXfPH>