From: Ulrich Mueller <ulm@gentoo.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Diego Petteno <flameeyes@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Emacs daemon dies at Xorg crash
Date: Fri, 19 Dec 2008 01:04:29 +0100 [thread overview]
Message-ID: <18762.58637.46084.413096@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <200812182249.mBIMnYK6014142@mothra.ics.uci.edu>
>>>>> On Thu, 18 Dec 2008, Dan Nicolaescu wrote:
>> > Can you try the patch at:
>> > http://permalink.gmane.org/gmane.emacs.bugs/22201
>>
>> Tested and Emacs doesn't die anymore. I find the "Connection lost ..."
>> message in the *Messages* buffer after reconnecting.
> IMO that patch is good, but it fixes the effect in this case, not the
> cause.
Hm, could you please elaborate what you mean by "effect" and "cause"
here?
>> #0 Fsignal (error_symbol=0x84863b9, data=0x874d62d) at eval.c:1640
>> #1 0x0824c780 in xsignal (error_symbol=0x84863b9, data=0x874d62d) at eval.c:1772
>> #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
This error has nothing to do with the X connection problem, right?
> Can you please check why the above function fails?
server-start gets called from kill-emacs-hook. It first deletes the
server-process, and then calls server-running-p, which unsuccessfully
tries to connect to the server's socket (server.el, revision 1.177):
(when server-process
;; kill it dead!
(ignore-errors (delete-process server-process)))
;; Delete the socket files made by previous server invocations.
(if (not (eq t (server-running-p server-name)))
However, please note that make-network-process in server-running-p is
inside a condition-case. (Which doesn't prevent it from hitting my
gdb breakpoint in Fsignal.)
> Can you also revert server.el to version 1.175 and see if that still
> causes problems?
With 1.175 it doesn't hit Fsignal. But I'm not sure if there really is
a problem in 1.177.
Ulrich
next prev parent reply other threads:[~2008-12-19 0:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1229454957.21129.0.camel@localhost>
2008-12-17 11:10 ` Emacs daemon dies at Xorg crash Ulrich Mueller
2008-12-17 11:37 ` dhruva
2008-12-17 16:03 ` Chong Yidong
2008-12-17 17:08 ` Dan Nicolaescu
2008-12-17 19:25 ` Ulrich Mueller
2008-12-17 22:51 ` Dan Nicolaescu
2008-12-18 12:03 ` Ulrich Mueller
2008-12-18 12:14 ` Ulrich Mueller
2008-12-18 19:14 ` Dan Nicolaescu
2008-12-18 22:03 ` Ulrich Mueller
2008-12-18 22:49 ` Dan Nicolaescu
2008-12-19 0:04 ` Ulrich Mueller [this message]
2008-12-19 0:46 ` Dan Nicolaescu
2008-12-19 8:00 ` Ulrich Mueller
2008-12-19 17:00 ` Dan Nicolaescu
2008-12-19 17:27 ` Ulrich Mueller
2008-12-19 17:47 ` Dan Nicolaescu
2008-12-19 13:56 ` Stefan Monnier
2008-12-19 16:45 ` Dan Nicolaescu
2008-12-20 18:35 ` Ulrich Mueller
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18762.58637.46084.413096@a1ihome1.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=cyd@stupidchicken.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=flameeyes@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).