系统什么时候发送sigkill信号

 

My application sometimes randomly receives a SIGKILL signal, gdb would

say something like:

Program terminated with signal SIGKILL, Killed.

The program no longer exists.

(gdb)

And i have no clue why? When does the system send a SIGKILL? There is

no 3rd application send anything to mine....

 

 

There are situations under which the kernel will send SIGKILL to a
process. Others have mentioned the Linux OOM killer; a more rarely
seen one is if you have a CPU-time resource hard limit set (such as
via the ulimit shell-builtin) then the kernel will send the process a
SIGKILL when the limit is reached.(内存泄漏和cpu-time超过硬件

限制时将导致进程被kill掉)

Another fairly 'standard' case is when the process tracing another
process using ptrace() dies without stopping the tracing; the traced
process is sent a SIGKILL then. Since the process in this case is
being actively traced with gdb, that would apparently not apply here,
but it does explain why killing gdb will kill a process that gdb is
attached to.(这就可以解释为什么kill掉gdb时，gdb调试的进程将

一起被kill掉)

Other possibilities to consider:
- bad memory hardware (usually results in SIGSEGVs, but it looks
like there are cases where SIGKILL will be generated)
- network or pseudo filesystem being ripped out from under the
process
- hit the SysReq key
- various "secure computing" setups which restrict the operations
a process can use

Good luck!


Philip Guenther