From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ulrich Mueller Newsgroups: gmane.emacs.devel Subject: Re: Emacs daemon dies at Xorg crash Date: Fri, 19 Dec 2008 18:27:03 +0100 Message-ID: <18763.55655.852333.725237@a1ihome1.kph.uni-mainz.de> References: <1229454957.21129.0.camel@localhost> <18760.56870.137654.853165@a1ihome1.kph.uni-mainz.de> <87k59yssad.fsf@cyd.mit.edu> <200812171708.mBHH8hPO008789@mothra.ics.uci.edu> <18761.21020.890676.865384@a1ihome1.kph.uni-mainz.de> <200812172251.mBHMp3ce010724@mothra.ics.uci.edu> <18762.15396.428952.119630@a1i15.kph.uni-mainz.de> <200812181914.mBIJE7qb013842@mothra.ics.uci.edu> <18762.51405.911216.76307@a1ihome1.kph.uni-mainz.de> <200812182249.mBIMnYK6014142@mothra.ics.uci.edu> <18762.58637.46084.413096@a1ihome1.kph.uni-mainz.de> <200812190046.mBJ0k7Im014390@mothra.ics.uci.edu> <18763.21652.870274.903036@a1ihome1.kph.uni-mainz.de> <200812191700.mBJH02YT016405@mothra.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1229707765 31937 80.91.229.12 (19 Dec 2008 17:29:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Dec 2008 17:29:25 +0000 (UTC) Cc: Chong Yidong , Diego Petteno , emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 19 18:30:29 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LDjAR-0001Og-Tu for ged-emacs-devel@m.gmane.org; Fri, 19 Dec 2008 18:29:40 +0100 Original-Received: from localhost ([127.0.0.1]:60215 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LDj9F-00051O-E9 for ged-emacs-devel@m.gmane.org; Fri, 19 Dec 2008 12:28:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LDj80-0004j7-JO for emacs-devel@gnu.org; Fri, 19 Dec 2008 12:27:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LDj7z-0004iV-29 for emacs-devel@gnu.org; Fri, 19 Dec 2008 12:27:08 -0500 Original-Received: from [199.232.76.173] (port=49378 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LDj7y-0004iQ-O4 for emacs-devel@gnu.org; Fri, 19 Dec 2008 12:27:06 -0500 Original-Received: from a1iwww1.kph.uni-mainz.de ([134.93.134.1]:59937) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LDj7y-0002M3-8M for emacs-devel@gnu.org; Fri, 19 Dec 2008 12:27:06 -0500 Original-Received: from a1ihome1.kph.uni-mainz.de (a1ihome1.kph.uni-mainz.de [134.93.134.75]) by a1iwww1.kph.uni-mainz.de (8.14.0/8.13.4) with ESMTP id mBJHR4Tj023770; Fri, 19 Dec 2008 18:27:04 +0100 Original-Received: from a1ihome1.kph.uni-mainz.de (localhost [127.0.0.1]) by a1ihome1.kph.uni-mainz.de (8.14.0/8.14.1) with ESMTP id mBJHR3T3022685; Fri, 19 Dec 2008 18:27:03 +0100 Original-Received: (from ulm@localhost) by a1ihome1.kph.uni-mainz.de (8.14.0/8.14.0/Submit) id mBJHR3Y4022680; Fri, 19 Dec 2008 18:27:03 +0100 In-Reply-To: <200812191700.mBJH02YT016405@mothra.ics.uci.edu> X-Mailer: VM 8.0.2-487 under Emacs 22.2.1 (i686-pc-linux-gnu) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107070 Archived-At: >>>>> On Fri, 19 Dec 2008, Dan Nicolaescu wrote: >> But "X connection lost" is precisely what happens. What could Emacs do >> to prevent this, if there is suddenly no X server anymore? > Kill the frames on the display that was closed and continue running? But it does that? The error occurs _after_ deleting these frames. Or am I missing something here? > Your backtrace seems to show that the problem happens because of > Fmake_network_process... I think that this is an unrelated problem. (In fact, I'd better set a breakpoint in Fkill_emacs, and you wouldn't have seen that part of the backtrace at all.) Here are the relevant frames of the backtrace again: #2 0x081f8844 in report_file_error (string=0x82e8afa "make client process failed", data=0x874d675) at fileio.c:277 #3 0x0829a4bd in Fmake_network_process (nargs=0xa, args=0x7f877cd0) at process.c:3632 [...] #42 0x0824debd in Frun_hooks (nargs=0x1, args=0x7f8793f4) at eval.c:2591 [...] #45 0x081c1a14 in Fkill_emacs (arg=0xfffffff8) at emacs.c:2087 #46 0x081c3219 in cmd_error_internal (data=0x874618d, context=0x7f87946e "") at keyboard.c:1274 Fkill_emacs is called because cmd_error_internal doesn't like to output the error message ("Connection lost ...") to the initial frame. Fmake_network_process is called later, while running kill-emacs-hook. This is unrelated to the original error. Ulrich