From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126 Date: Thu, 06 Dec 2012 22:25:29 +0200 Message-ID: <831uf3orly.fsf@gnu.org> References: <50BFA054.1060503@optusnet.com.au> <83r4n4p4wt.fsf@gnu.org> <50BFFD14.5010102@cs.ucla.edu> <83pq2nq1ml.fsf@gnu.org> <50C02815.1050002@cs.ucla.edu> <83ehj3ox1p.fsf@gnu.org> <50C0FD9C.7040203@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1354825615 9192 80.91.229.3 (6 Dec 2012 20:26:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Dec 2012 20:26:55 +0000 (UTC) Cc: 13086@debbugs.gnu.org, stephen_powell@optusnet.com.au To: Paul Eggert Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Dec 06 21:27:08 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tgi2B-0007my-Av for geb-bug-gnu-emacs@m.gmane.org; Thu, 06 Dec 2012 21:27:03 +0100 Original-Received: from localhost ([::1]:42165 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tgi1z-0008FZ-3Y for geb-bug-gnu-emacs@m.gmane.org; Thu, 06 Dec 2012 15:26:51 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:39312) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tgi1w-0008FU-Qf for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2012 15:26:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tgi1v-000188-Kc for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2012 15:26:48 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:47009) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tgi1v-000183-HD for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2012 15:26:47 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1Tgi29-0000Py-Od for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2012 15:27:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 Dec 2012 20:27:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13086 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13086-submit@debbugs.gnu.org id=B13086.13548255731551 (code B ref 13086); Thu, 06 Dec 2012 20:27:01 +0000 Original-Received: (at 13086) by debbugs.gnu.org; 6 Dec 2012 20:26:13 +0000 Original-Received: from localhost ([127.0.0.1]:57260 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Tgi1N-0000Oy-GD for submit@debbugs.gnu.org; Thu, 06 Dec 2012 15:26:13 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:33461) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Tgi1L-0000Oq-Nd for 13086@debbugs.gnu.org; Thu, 06 Dec 2012 15:26:12 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MEM00100LZ21000@a-mtaout22.012.net.il> for 13086@debbugs.gnu.org; Thu, 06 Dec 2012 22:25:33 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MEM000TUM2HA6D0@a-mtaout22.012.net.il>; Thu, 06 Dec 2012 22:25:30 +0200 (IST) In-reply-to: <50C0FD9C.7040203@cs.ucla.edu> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:68054 Archived-At: > Date: Thu, 06 Dec 2012 12:18:36 -0800 > From: Paul Eggert > CC: stephen_powell@optusnet.com.au, 13086@debbugs.gnu.org > > On 12/06/12 10:28, Eli Zaretskii wrote: > > Yes, but we usually do that only if Emacs cannot possibly recover from > > that internal error. If Emacs _can_ continue, then we only abort via > > eassert, so that a production version won't crash. > > Well, it depends on what "recovery" means. In this case, if > Emacs ignores the error and continues, it will have a confused > data structure that can cause it to kill unrelated innocent-victim > processes seemingly at random. How can that happen, if PID is not our child process? And even if it does happen, the hypothetical problem you envision hardly justify losing an Emacs session. > One possibility is for Emacs to fall back into recovery mode, such > as what it does now when it runs out of memory. That is, Emacs > would tell you that it has had an internal error and that you should > save your work and exit as soon as you can. This would lessen > the likelihood of the confused Emacs causing further damage. It is much easier to remove the offending process object from the list of those we expect to be dead.