memory limits....

[adler at stephenadler.com (Stephen Adler)]

Thanks for the reply. I'm using malloc, under gcc 3.2, red hat,
enterprise linux 3, kernel 2.4. After allocating about 2.4 Gigs,
subsequent malloc's return NULL. I check for NULL returns from
my malloc's and exit my code if this condition is met. The OS
seems to be happy, nothing grinds to a halt. My applications
allocates all the needed memory at startup, so if not enough
is allocated, it informs the user and exits.

On Thu, 2005-05-19 at 10:20, David Backeberg wrote:
> There are limits hiding out in all kinds of places, you just don't run 
> into most of them on a daily basis. You have to figure out which limit
> you're bumping against:
> 
> what language?
> what compiler?
> what architecture?
> 
> There are limits in data structures, data types within a language, kernel 
> versions, filesystems, compilers, blah, blah, blah.
> 
> What happens when you hit your limit? The system grinds to a halt? It 
> core dumps?