Date: Tue, 17 Aug 1999 08:46:13 -0600 From: Charles Randall <crandall@matchlogic.com> To: freebsd-hackers@FreeBSD.ORG Subject: RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE Message-ID: <64003B21ECCAD11185C500805F31EC0303786D2A@houston.matchlogic.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64003B21ECCAD11185C500805F31EC0303786D2A>