"killed" Message - how to trace/back trace
Hi Friends,
When I run my code (its C Code, its quite huge stack with around 10 threads/tasks), because of some memory/task issue I get "killed" message from the kernel (I assume that this is from the kernel !). Is there a way to trace/back trace the problem and find the cause/location of bug or atleast some level of knowledge by which I can figure out the issue. Just to add, this is my first question to the forum ! Thanks in advance ! and Hi to all ! ./Ebin |
There is probably an oom_killer (out of memory) message in "dmesg".
Add some more swap space, and maybe use something like sar to track the memory usage increase. |
All times are GMT -5. The time now is 01:02 PM. |