On Wed, Aug 24, 2005 at 08:09:36AM -0500, Dave Feustel wrote: > On Wednesday 24 August 2005 07:04, Hannah Schroeter wrote: > > > 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? > --
Those programs use mmap() to create their basic image and fill it in. Then on a later invocation, they try to use mmap() again to get the image at the same location, which works on most Unix systems, except for OpenBSD-current...
