Re: HEADS UP: Merge of binutils 2.17

On 2011-01-08 01:54, Anonymous wrote:
> Looks like lang/sbcl doesn't like new ld(1), here on amd64.
> Same error when building using devel/binutils. Can you reproduce?
...
>    //doing warm init - compilation phase
>    This is SBCL 1.0.43, an implementation of ANSI Common Lisp.
>    More information about SBCL is available at<http://www.sbcl.org/>.
>
>    SBCL is free software, provided as is, with absolutely no warranty.
>    It is mostly in the public domain; some portions are provided under
>    BSD-style licenses.  See the CREDITS and COPYING files in the
>    distribution for more information.
>    Bus error

Yes, it gives a bus error here too, at least on amd64.  I found a
similar thread about such an issue with sbcl, started by you in March
2009:

http://lists.freebsd.org/pipermail/freebsd-current/2009-March/004690.html

It looks like in this case, the same problem happens, it eats large
amounts of memory, and then dies (this is on a box with 4G RAM and a few
G of swap):

   PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
33512 dim           1 111    0  8244M  3055M CPU1    1   0:54 68.99% sbcl

Obviously, when it tries to actually access stuff that is above the
total virtual memory of the box, it will die.

In any case, the workaround in that previous thread (setting  the sysctl
machdep.prot_fault_translation=2) works for me, at least to let the port
build to completion, and install succesfully.

Now, in the previous report, it seems there was something going on with
.note.ABI-tag sections, which needed a kernel fix.  And since Kostik is
now introducing new .note sections, for the non-executable stack
feature, it may be that I just hit a window where it is not entirely
complete?

The last sync of binutils-2.17 with head was at r217118, just after the
introduction of those .note sections, but before several related changes
in the kernel and other areas.  I will sync the binutils-2.17 branch
again, and see if that helps the port to build without setting the
workaround sysctl.