From owner-freebsd-current Wed Apr 14 8:20:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7AC76151E1 for ; Wed, 14 Apr 1999 08:20:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA29357; Wed, 14 Apr 1999 17:17:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA00773; Wed, 14 Apr 1999 17:17:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Wed, 14 Apr 1999 11:01:03 EDT." <199904141501.LAA25847@kot.ne.mediaone.net> Date: Wed, 14 Apr 1999 17:17:39 +0200 Message-ID: <771.924103059@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904141501.LAA25847@kot.ne.mediaone.net>, Mikhail Teterin writes: >Poul-Henning Kamp once stated: > >=malloc() on FreeBSD returns NULL when it cannot allocate the memory >=asked for. > >=If you have an example where this is not the case I would VERY >=much like to see it. > >I believe, a number of examples were given, when the use of the non-NULL >pointer returned by malloc resulted in the program being killed. No, the examples I have seen showed the system killing a (somewhat) random large process in an attempt to avoid deadlock. I guess you can interpret it the way above if you insist on using a very narrow application oriented focus. Ignoring the larger issues is not a modus operandi I subscribe to. Anyway, what you're asking for is really resource reservation. Sorry FreeBSD doesn't support resource reservation for memory. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message