|
From: | Dmitry Antipov |
Subject: | bug#16093: 24.3.50; Crash of emacs --daemon on killing X server |
Date: | Mon, 09 Dec 2013 21:57:59 +0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
On 12/09/2013 07:58 PM, Nix wrote:
Start emacs --daemon (using the lucid toolkit), under X. Shut X down. Emacs crashes shortly afterwards. The lack of symbol table info is concerning (obviously my gdb has forgotten how to look up separated debug info *yet again*), but I don't think that important, since the death site is after a (garbage-collect) thus not in Lisp-land anyway. Obviously no xbacktrace is possible: the process is dead. It is fairly clear that we should not be calling xftfont_close() if the X server is not there! Why has this started happening?
Hm... IIUC there is no convenient way to check whether X display connection is alive. But we can do some tricks, for example, try to select() or poll() ConnectionNumber() - if there is no EBADF, X server is hopefully present... Dmitry
bug16093.patch
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |