Dag-Erling Smorgrav <[EMAIL PROTECTED]> wrote: > >This is all academic since FreeBSD does memory overcommit, so unless >you run out of address space for your process before you run out of >actual memory and/or swap (not likely, but quite possible) malloc() >will never return NULL and you won't know a thing until you dirty one >page too many and segfault. What about setrlimit(RLIMIMT_DATA)? Tony. -- f.a.n.finch [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Setting memory allocator... Matt Dillon
- Re: Setting memory allocator... Peter Seebach
- Re: Setting memory allocator... Rik van Riel
- Re: Setting memory allocator... Peter Seebach
- Re: Setting memory allocator... Rik van Riel
- Re: Setting memory allocator... Peter Seebach
- Re: Setting memory allocator... Peter Seebach
- Re: Setting memory allocators for library... Julian Elischer
- Re: Setting memory allocators for lib... Daniel C. Sobral
- Re: Setting memory allocators fo... Dag-Erling Smorgrav
- Re: Setting memory allocators for library fun... Tony Finch
- Re: Setting memory allocators for library... Dag-Erling Smorgrav
- Re: Setting memory allocators for library functions. Thomas David Rivers
- Re: Setting memory allocators for library functions. michael schuster

