From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; Emacs should survive a lost X connection Date: Wed, 06 Feb 2008 14:20:55 -0500 Message-ID: References: <20080205.155847.56398348.hanche@math.ntnu.no> <200802051957.m15Jv8r1019258@sallyv1.ics.uci.edu> <200802052349.m15NnxSu013983@sallyv1.ics.uci.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1202325917 16863 80.91.229.12 (6 Feb 2008 19:25:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 6 Feb 2008 19:25:17 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, hanche@math.ntnu.no To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 06 20:25:39 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 1JMptQ-0001Nt-Oe for ged-emacs-devel@m.gmane.org; Wed, 06 Feb 2008 20:25:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JMpsy-0001HZ-Bp for ged-emacs-devel@m.gmane.org; Wed, 06 Feb 2008 14:24:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JMppK-000882-KM for emacs-devel@gnu.org; Wed, 06 Feb 2008 14:20:58 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JMppJ-00087K-5y for emacs-devel@gnu.org; Wed, 06 Feb 2008 14:20:58 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JMppI-00087E-Li for emacs-devel@gnu.org; Wed, 06 Feb 2008 14:20:56 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JMppI-0001WP-E0 for emacs-devel@gnu.org; Wed, 06 Feb 2008 14:20:56 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1JMppH-0008LZ-63; Wed, 06 Feb 2008 14:20:55 -0500 In-reply-to: <200802052349.m15NnxSu013983@sallyv1.ics.uci.edu> (message from Dan Nicolaescu on Tue, 05 Feb 2008 15:49:49 -0800) 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:88352 gmane.emacs.pretest.bugs:20906 Archived-At: * eval.c (internal_condition_case_2, internal_condition_case_1) (internal_condition_case): Reenable abort if x_catching_errors () to see if that really happens and why. Richard, now you have part of the answer: if the X11 connection is lost emacs crashes after your patch. It works fine after undoing the patch. Interesting. Can you send me a backtrace for that crash? (Undoing this patch also solves another issue discussed recently: emacs crashes after using xkill on an emacsclient frame). I'd like to see a backtrace for that case too. The idea is, if there is a good reason for those calls to be where they are, then the right thing is to undo my patch and add comments explaining in detail why it is legitimate for those functions to be called with x_catching_errors in effect. But if it is clean to get rid of those calls, and handle those cases differently, that is better.