> > 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
- Probably bug with allocation memory in FreeBSD-3.2-RELEASE Alec Kalinin
- Re: Probably bug with allocation memory in FreeBSD-3.... Mark Newton
- Re: Probably bug with allocation memory in FreeBS... Biju Susmer
- Re: Probably bug with allocation memory in Fr... Mark Newton
- Re: Probably bug with allocation memory in FreeBSD-3.... Alec Kalinin
- Re: Probably bug with allocation memory in FreeBS... Ilia Chipitsine
- Re: Probably bug with allocation memory in Fr... Oleg Derevenetz
- RE: Probably bug with allocation memory in FreeBSD-3.... Charles Randall