From: Willy Tarreau <willy@w.ods.org>
To: Ram Gupta <ram.gupta5@gmail.com>
Cc: James Courtier-Dutton <James@superbug.demon.co.uk>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: X killed
Date: Tue, 17 Jan 2006 22:41:49 +0100 [thread overview]
Message-ID: <20060117214149.GA30467@w.ods.org> (raw)
In-Reply-To: <728201270601171332v6c95df17u167d15212dde66c4@mail.gmail.com>
On Tue, Jan 17, 2006 at 03:32:11PM -0600, Ram Gupta wrote:
> On 1/17/06, James Courtier-Dutton <James@superbug.demon.co.uk> wrote:
> > 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?
>
> You may try using strace . It may throw some light on the cause of the problem.
I would particularly suggest using 'strace -tt' both on X and on the
python process. It will make it easier to analyse the causes later. You
might even encounter a bug in the python application causing an explicit
kill of a miscalculated pid (although unlikely, but who knows ?).
> Regards
> Ram gupta
Regards,
Willy
next prev parent reply other threads:[~2006-01-17 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 17:36 X killed James Courtier-Dutton
2006-01-15 19:27 ` Willy Tarreau
2006-01-17 12:40 ` James Courtier-Dutton
2006-01-17 20:12 ` Jan Engelhardt
2006-01-17 20:17 ` Lee Revell
2006-01-19 16:06 ` Nix
2006-01-17 20:54 ` James Courtier-Dutton
2006-01-17 21:32 ` Ram Gupta
2006-01-17 21:41 ` Willy Tarreau [this message]
2006-01-19 11:09 ` James Courtier-Dutton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060117214149.GA30467@w.ods.org \
--to=willy@w.ods.org \
--cc=James@superbug.demon.co.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ram.gupta5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox