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#8472: 24.0.50; weird emacs bugs causing data lossage Date: Mon, 11 Apr 2011 05:36:06 -0400 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1302514670 18438 80.91.229.12 (11 Apr 2011 09:37:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 11 Apr 2011 09:37:50 +0000 (UTC) Cc: 8472@debbugs.gnu.org To: joakim@verona.se Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Apr 11 11:37:45 2011 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Q9DYt-0005KQ-1t for geb-bug-gnu-emacs@m.gmane.org; Mon, 11 Apr 2011 11:37:45 +0200 Original-Received: from localhost ([127.0.0.1]:33498 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q9DYr-0005HH-B2 for geb-bug-gnu-emacs@m.gmane.org; Mon, 11 Apr 2011 05:37:33 -0400 Original-Received: from [140.186.70.92] (port=43972 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q9DYg-0005EF-Fb for bug-gnu-emacs@gnu.org; Mon, 11 Apr 2011 05:37:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q9DYe-0004Ai-GN for bug-gnu-emacs@gnu.org; Mon, 11 Apr 2011 05:37:21 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:41817) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9DYe-0004Ab-ES for bug-gnu-emacs@gnu.org; Mon, 11 Apr 2011 05:37:20 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1Q9DYM-0001Ic-Gt; Mon, 11 Apr 2011 05:37:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 11 Apr 2011 09:37:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 8472 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 8472-submit@debbugs.gnu.org id=B8472.13025145744937 (code B ref 8472); Mon, 11 Apr 2011 09:37:02 +0000 Original-Received: (at 8472) by debbugs.gnu.org; 11 Apr 2011 09:36:14 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Q9DXZ-0001Ha-Qu for submit@debbugs.gnu.org; Mon, 11 Apr 2011 05:36:14 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Q9DXY-0001HO-Lq for 8472@debbugs.gnu.org; Mon, 11 Apr 2011 05:36:13 -0400 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Q9DXS-00087S-Qb; Mon, 11 Apr 2011 05:36:06 -0400 In-reply-to: (joakim@verona.se) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Mon, 11 Apr 2011 05:37:02 -0400 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:45754 Archived-At: > From: joakim@verona.se > Cc: 8472@debbugs.gnu.org > Date: Mon, 11 Apr 2011 11:25:23 +0200 > > I got it working by suspending gdb and resuming it again. and sending > signals to Emacs (I was a bit furious so this part is a bit hazy) So from that point on, please use the procedure in etc/DEBUG to find out where it is looping. > Ok. So the hang happens somewhere else. The symptom is that nothing > happens on the display but emacsclient can communicate. Do you remember what was displayed in the minibuffer at that point, by any chance? Was it a single screen line or more than that? Or maybe only part of the text was visible, i.e. Emacs froze when it tried to enlarge (a.k.a. "resize") the echo area? > Also, whenever I manage to break into the process with gdb the backtrace > shows Emacs is in the select call. With strace I see that Emacs is not > stuck there but loops. This is normal, or at least it could be normal: Emacs usually checks for any arriving input from any possible sources, and that includes calls to `select'. Seeing a lot of calls to `select' is not in itself a sign of an infloop. Only the procedure in etc/DEBUG (or something similar) can give a definitive answer to that. > So I figure theres some poll loop running closely around the select. Emacs does that all the time, that's how it knows that input arrived from a subprocess or a socket, for example. It polls. > >> - the file was truncated. Maybe this is due to a combination of > >> narrowing and automatic save. > > > > Can't happen, auto-save forces temporary widening of the buffer (as > > you'd expect ;-). > > Well. The funny thing is that the truncated content of the file is the > exact same content I see in the narrowed buffer on screen. > > Org narrows in another window and buffer somehow. Could that interfere? > I dont know the term for what it does yet. "indirect buffer" maybe? Could be. IOW, if auto-save happened in a buffer whose contents was just the text you found in the auto-save file.