From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; Emacs should survive a lost X connection Date: Thu, 07 Feb 2008 23:26:05 -0800 Message-ID: <200802080726.m187Q5gL002961@sallyv1.ics.uci.edu> References: <20080205.155847.56398348.hanche@math.ntnu.no> <200802051957.m15Jv8r1019258@sallyv1.ics.uci.edu> <200802052349.m15NnxSu013983@sallyv1.ics.uci.edu> <200802062007.m16K7r78005498@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1202455668 18224 80.91.229.12 (8 Feb 2008 07:27:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Feb 2008 07:27:48 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, hanche@math.ntnu.no To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 08 08:28:10 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 1JNNeb-0001bp-Gr for ged-emacs-devel@m.gmane.org; Fri, 08 Feb 2008 08:28:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNNe8-0002Rt-Nc for ged-emacs-devel@m.gmane.org; Fri, 08 Feb 2008 02:27:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JNNe2-0002QE-Sh for emacs-devel@gnu.org; Fri, 08 Feb 2008 02:27:34 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JNNdz-0002Ls-TK for emacs-devel@gnu.org; Fri, 08 Feb 2008 02:27:34 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNNdz-0002Lc-JG for emacs-devel@gnu.org; Fri, 08 Feb 2008 02:27:31 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JNNdz-0004Yb-9j for emacs-devel@gnu.org; Fri, 08 Feb 2008 02:27:31 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JNNdy-0005lS-JY for emacs-pretest-bug@gnu.org; Fri, 08 Feb 2008 02:27:30 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JNNdv-0004XL-BS for emacs-pretest-bug@gnu.org; Fri, 08 Feb 2008 02:27:30 -0500 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JNNdu-0004WR-PA; Fri, 08 Feb 2008 02:27:27 -0500 X-ICS-MailScanner-Watermark: 1203060367.84519@54omgzXQdzv1PqqaWp57xw Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m187Q5gL002961; Thu, 7 Feb 2008 23:26:05 -0800 (PST) In-Reply-To: (Richard Stallman's message of "Thu, 07 Feb 2008 23:16:14 -0500") Original-Lines: 12 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:88505 gmane.emacs.pretest.bugs:20943 Archived-At: Richard Stallman writes: > The crash is caused by the code in Fdelete_frame > to call the hook `delete-frame-functions'. > I don't think that should be done while handling a disconnect > in a signal handler. So I changed it so that FORCE inhibits that. > > Are there any more crashes due to that error check? No, the crashes are gone. But the server does not seem to know that the clients have gone, it gives a warning when trying to exit because it thinks that clients are still connected.