From: Nikodemus S. <nik...@ra...> - 2009-04-22 17:37:53
|
2009/4/13 Ken Olum <kd...@co...>: > 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 > relevant. SBCL *should* be taking care of this on its own, assuming that it correctly figures that it is necessary. What does the attached bit of C say of about your system? (Copy-pasted from the code SBCL used to see if re-execing with a different personality is needed.) > Ideally, sbcl would be fixed to not require space into which mapped > memory will be randomized. Quite. This is a long-standing TODO. Cheers, -- Nikodemus |