Re: X killed

[James Courtier-Dutton <James@superbug.demon.co.uk>]

Willy Tarreau wrote:
> Hi,
> 
> On Sun, Jan 15, 2006 at 05:36:59PM +0000, James Courtier-Dutton wrote:
> 
>>Hi,
>>
>>I have a python application that kills X. I.e. the X process terminates, 
>>and all X programs receive broken links to the display and therefore 
>>also exit.
>>
>>The problem is, this python application is not supposed to kill 
>>anything, so I think it is a bug in X, but I cannot find any way to 
>>trace the fault. Even gdb says the application was killed, so exited 
>>normally, and results in no back trace.
>>
>>Is there any way in Linux to find out who did the "killing" ?
> 
> 
> Probably that X was killed because your system encountered an OOM
> (out of memory) condition. For instance, if python eats all the
> memory, and if you have not set any memory usage limit with ulimit,
> then you can get anything killed.
> 
> 
>>James
> 
> 
> Willy
> 
> 
> 

My point is that there is no way to tell what kills me. No messages in 
syslog...nothing. Surely the OOM killer would send a message to ksyslog, 
or at least dmesg?

James