>> I was writing a program there that when it called a library, it went
> spastic mallocing memory. It did this is VERY damn quick and used to crash
> the linux box within 10 seconds if not stopped. It managed to kill INIT
> once and the results were not pleasant in the slightest. Thing is, how can
> I stop a program doing something like this. I have the problem solved so
> it doesn't crash but it's very bad form that linux allowed itself to be
> brought down in this fashion by a user space process. Ideas for
Err... the program itself went bananas, or the library it called did so?
There's no way in hell *any* user space program under Linux should be
capable of doing that : it should run out of virtual memory and get
If you can reproduce it reliably, report it as a bloody serious bug.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!