> I have experimented the same issue but it is not kernel related. It is
> due to the use of jemalloc in current instead of the old malloc
> implementation. Clisp seems to do some evil assumption about what malloc
> does.
> 
> There is two workaround possible. Rebuild libc using USE_JEMALLOC=NO or
> use the good configure flag for clisp ( --with-gmalloc ). The clisp
> package has been updated to use this flag so I think that if you rebuild
> clisp, everything will be fine.

Is --with-gmalloc a standard configureism? If so, we may wish to put
something into the headers (or whatever) to fake a false positive for
gmalloc, if it avoids further issues with other software.