We are trying to switch to a mmap-based malloc implementation.
This interferes with clisp like this:
./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -norc -m
1000KW -M interpreted.mem -q -c compiler.lisp
Cannot map memory to address 0xe833f000 .
errno = EINVAL: Invalid argument.
Looking through clisp source, I find several places where this
string occurs. I could use a small roadmap to track this issue
down: what does clisp do with mmap'ing stuff to fixed addresses,
and how can I influence it to mmap stuff to legitimate addresses
under the new scheme ?