From owner-freebsd-hackers Tue Aug 17 7:47:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 816661564F for ; Tue, 17 Aug 1999 07:47:05 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2448.0) id ; Tue, 17 Aug 1999 08:46:19 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC0303786D2A@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@FreeBSD.ORG Subject: RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE Date: Tue, 17 Aug 1999 08:46:13 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The program in question does attempt to core dump when trying to fill the memory returned from malloc when malloc returns null. It almost seems like the attempt to dump core in an "out of swap" condition causes what seems like a machine hang (although you can still ping the machine). Charles -----Original Message----- From: Biju Susmer [mailto:bee@wipinfo.soft.net] Sent: Tuesday, August 17, 1999 3:25 AM Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE > > 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? -biju To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message