Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash

[wg@malloc.de]

> > In general, if you want malloc to return NULL on Linux in a controlled
> > way, the best advice is to use "ulimit -v" IMHO.
> 
> No, this is really a very bad idea, as this would limit the virtual
> memory, instead of checks being done dynamically.

Oh, so you're adding/removing physical memory dynamically?

> And the memory will
> quickly be exhausted.

Well, either live with that or add sufficient swap space.

Regards,
Wolfram.