Juho Snellman <jsnell@...> writes:
> Sounds like an issue with the memory map randomization that some
> kernels do to "improve" security. In normal kernels this randomization
> is only done in versions 2.6.11 and later, for which SBCL implements a
> workaround. But the kernel on that machine seems to be a Red Hat
> kernel, which had that feature enabled even in earlier releases. Try
> running sbcl as "setarch i386 sbcl" or "setarch i386 -R sbcl"
> (depending on how old that RHEL installation really is).
Maybe the 'try "ulimit -a"' message should also suggest these other
workarounds to be tried?