Date: Sun, 15 Jan 2006 20:27:11 +0100
From: Willy Tarreau <willy@w.ods.org>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: X killed
Message-ID: <20060115192711.GO7142@w.ods.org>
References: <43CA883B.2020504@superbug.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43CA883B.2020504@superbug.demon.co.uk>
User-Agent: Mutt/1.5.10i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1062
Lines: 30

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

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