From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: X killed
Date: Sun, 15 Jan 2006 17:36:59 +0000 [thread overview]
Message-ID: <43CA883B.2020504@superbug.demon.co.uk> (raw)
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" ?
James
next reply other threads:[~2006-01-15 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 17:36 James Courtier-Dutton [this message]
2006-01-15 19:27 ` X killed 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
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=43CA883B.2020504@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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