From owner-freebsd-hackers Tue Aug 17 7:49: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id BA97D14F1C for ; Tue, 17 Aug 1999 07:47:39 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id AAA71878; Wed, 18 Aug 1999 00:17:12 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199908171447.AAA71878@gizmo.internode.com.au> Subject: Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE To: bee@wipinfo.soft.net Date: Wed, 18 Aug 1999 00:17:12 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <008801bee892$5703f920$88291fac@wipro.tcpn.com> from "Biju Susmer" at Aug 17, 99 02:54:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Biju Susmer wrote: > > Well, yeah, that's becuase you're running it out of swap by trying to > > allocate a gigabyte of memory. > > but this is done in steps of 1MB. Once it reaches out of memory, malloc > should return NULL. Since there is no checking for NULL in this code, > it should hit a signal, isn't it? Why that is not happening? We only had this thread a week ago. Please consult the archives. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message