Quoth Brian Feldman on Wed, 14 April: : : ACTUALLY it would still break ANSI because the malloc itself would crash : the program, instead of touching the memory manually.
The point here is that malloc can return null when it fails to allocate. I might mention that Andrew Reilly's suggestion is the winner so far, in my mind. The solution of having libc:malloc honor a 'setenv MALLOC_MMAP_STORE /path/here' would work with shrink-wrap software, and completely bypass the concerns, real and imagined, of even the most zealous advocate of overcommit purity. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message