Re: program killed

[Tony Clarke <tony.clarke@palamon.ie>]

Sounds like your system was tight on memory and the Memory Manager 
thought your
program was a good one to kill to recoup some scarce memory.

Have a look in /mm/oom_kill.c to see how it figures out who to kill.

>Hi there,
>
>Can anyone give me some hints about why my program is killed by system? I am 
>now debugging a program but after it runs for a while, I got a message saying 
>"Program terminated with signal SIGKILL, Killed". What's the causes? 
>Memory? I am the only user since I disconnected the computer (64 MB RAM) to 
>the network.  Last night I also run my program on my laptop (256 MB RAM), it 
>worked well when I used a part of data set (image). With the whole data the 
>program also got killed. I checked the syslog and found "VM: kill the program 
>XXX". I used MALLOC_CHECK_ but there is no memory abuse. Any suggestion?
>
>Many thanks in advance.
>
>QingHua
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>



******************************************************************************
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee.  Access to this e-mail by anyone else
is unauthorised.  If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful.
Please note that emails to, from and within RTÉ may be subject to the Freedom
of Information Act 1997 and may be liable to disclosure.
******************************************************************************
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html