Hello! On Sat, Aug 13, 2005 at 08:25:36AM +0200, Andreas Vögele wrote: >>Known problem, everybody does.
>Do you know if the OpenBSD kernel will be fixed before 3.8 is released? >Thierry Deval wrote on 4th May: >"While a proper solution has to be devised, you can use the following >diff that diminishes the impact of randomization on malloc... And makes >clisp work again. [...]" >I still use the patch that Thierry provided. I've received the suggestion to build clisp with these Makefile's CFLAGS: -DNO_SINGLEMAP -DNO_TRIVIALMAP -DNO_MULTIMAP_FILE -DNO_MULTIMAP_SHM However I don't know how to pass them in using the port, and I didn't have the time/energy to try it out. However I've been advised that that'll decrease the performance of clisp, among others it'll make the GC non-generational. Btw, doesn't that high degree of mmap randomization cause the virtual memory space, especially on 32-bit machines, to be quite fragmented, so big allocations might fail? And... While clisp seems to be the only port/package affected by all that randomization stuff, there *are* other things affected, such as cmucl/sbcl, just that they're not in ports anyway. But there were discussions on how to fix/workaround problems for similar randomization (in that case shared library load address randomization) on some "flavours" of Linux. Kind regards, Hannah.
