I'm running under Red Hat Enterprise Linux Server release 5.2
(Tikanga), i.e. 2.6.18-92.1.6.el5 #1 SMP. Some fraction of the time,
depending on things I don't understand, the kernel puts some working
memory on top of the place where the core file belongs, causing sbcl
to give errors like "mmap: wanted 1044480 bytes at 0x20000000,
actually mapped at 0x2aaab0091000".
I believe "setarch -R" fixes this problem, but I wish I had not had to
spend a long time discovering this. Now that I know that setarch is
what I needed, I can see that it is mentioned in the INSTALL file, but
it talks about fedora and about segfaults, so it didn't seem obviously
Ideally, sbcl would be fixed to not require space into which mapped
memory will be randomized. But if that's impossible or too hard, a
simple improvement might be to put a message after the above message
in linux-os.c, saying something like "This may be caused by address
space randomization. Saying 'setarch -R sbcl' may fix it."
It would also be helpful not to print the hint about memory limits in
the case of wrong address, but only in the case of mmap failed.