> > A few things that get bitten are some packages doing their own and very > > different memory management, but can't avoid malloc altogether. > > That is ports/lang/clisp, that seems to be also gprolog > > Can you describe how these programs manage to seg fault doing their > memory management? How do they run now if they don't use malloc?
Most of those that fail assume that if malloc returns a predictable memory address sequence. Not even emacs does that (and you don't want to hear that rant :)
