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:[EMAIL PROTECTED]]
Sent: Tuesday, August 17, 1999 3:25 AM
Cc: [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
