Re: X killed

[Lee Revell]

On Tue, 2006-01-17 at 21:12 +0100, Jan Engelhardt wrote:
> >
> > 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?
> >
> Yes, OOM usually does printk(). So it depends on how you have syslog set 
> up (and the console loglevel - which is reponsible for bringing it right 
> to console).

I think you are missing the point - the problem is almost certainly NOT
an OOM condition as there's nothing in the logs.  It's a bug in the X
server.  The question is, how does one debug that.

Here is the original question again:

"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" ?"

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/