From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#24640: Crashes in 25.1 Date: Wed, 12 Oct 2016 22:15:59 +0300 Message-ID: <83d1j59y4w.fsf@gnu.org> References: <20161012180726.GA6818@marvin.cs.ucl.ac.uk> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1476299861 16834 195.159.176.226 (12 Oct 2016 19:17:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 12 Oct 2016 19:17:41 +0000 (UTC) Cc: 24640@debbugs.gnu.org, phillip.lord@russet.org.uk, rrt@sc3d.org To: Toby Cubitt Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 12 21:17:36 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1buP1o-00026g-Sw for geb-bug-gnu-emacs@m.gmane.org; Wed, 12 Oct 2016 21:17:25 +0200 Original-Received: from localhost ([::1]:35338 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1buP1n-0003jr-Ko for geb-bug-gnu-emacs@m.gmane.org; Wed, 12 Oct 2016 15:17:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57436) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1buP1W-0003eu-6h for bug-gnu-emacs@gnu.org; Wed, 12 Oct 2016 15:17:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1buP1S-0004ya-4j for bug-gnu-emacs@gnu.org; Wed, 12 Oct 2016 15:17:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:47164) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1buP1S-0004yP-1e for bug-gnu-emacs@gnu.org; Wed, 12 Oct 2016 15:17:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1buP1R-00075k-UM for bug-gnu-emacs@gnu.org; Wed, 12 Oct 2016 15:17:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 12 Oct 2016 19:17:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24640 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 24640-submit@debbugs.gnu.org id=B24640.147629979827224 (code B ref 24640); Wed, 12 Oct 2016 19:17:01 +0000 Original-Received: (at 24640) by debbugs.gnu.org; 12 Oct 2016 19:16:38 +0000 Original-Received: from localhost ([127.0.0.1]:53354 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1buP10-00074y-Az for submit@debbugs.gnu.org; Wed, 12 Oct 2016 15:16:38 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:38086) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1buP0y-00074l-OT for 24640@debbugs.gnu.org; Wed, 12 Oct 2016 15:16:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1buP0p-0004jG-ED for 24640@debbugs.gnu.org; Wed, 12 Oct 2016 15:16:27 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:33080) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1buP0p-0004j3-B1; Wed, 12 Oct 2016 15:16:23 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3465 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1buP0m-0006Wb-69; Wed, 12 Oct 2016 15:16:21 -0400 In-reply-to: <20161012180726.GA6818@marvin.cs.ucl.ac.uk> (message from Toby Cubitt on Wed, 12 Oct 2016 19:07:26 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.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" Xref: news.gmane.org gmane.emacs.bugs:124413 Archived-At: > Date: Wed, 12 Oct 2016 19:07:26 +0100 > Cc: phillip.lord@russet.org.uk, rrt@sc3d.org, 24640@debbugs.gnu.org > From: Toby Cubitt > > Does loading Reuben's history file using undo-tree-load-history starting > from emacs -Q trigger the crash? From the discussion, I'm guessing not... Reuben said no. And I see it in my debugging on his machine: the bug is triggered in a very specific place for a single file, although several other files have their undo-tree history read and restored. > > Well, one place where redisplay could be triggered is those messages > > about failure to load history, like this one (which actually happens > > during restoring Emacs sessions from Reuben's desktop file): > > > > Error reading undo-tree history from "/home/user/.emacs.d/undo-tree/.!home!user!Foo!Bar!baz!doc!yyy.tex.~undo-tree~" > > > > (I obfuscated a few directory names here to protect Reuben's privacy.) > > That's odd. That particular error message can only be triggered if one of > the two (read (current-buffer)) calls fails. It means the undo history > file exists, but `read' could not parse the contents into a lisp > expression (or errored for some other reason). > > This shouldn't be possible. Undo-tree uses `prin1` to write one hash and > one complicated lisp structure to the file when it saves history. The > lisp structure does have a read syntax. Unless the history file has been > modified outside of undo-tree, it should always be able to read these > back in. > > Normal situations, like failing to find an undo history file or detecting > that the file has changed since the history was written, trigger > different error messages. > > Maybe this is a red herring, since failing to read a lisp expression > shouldn't crash Emacs anyway. But it's odd to me that this message is > triggered at all... Your surprise is IMO a reason good enough to ask Reuben to send you the undo-tree history file for analysis. Who knows, it might even be the clue we are looking for. (I agree that the error alone should not, and most probably is not, the cause of the crash.) In the *Messages* buffer at the point of the crash, I see error messages like above for 2 more files (but only one of the 3 immediately precedes a crash in GC, although GC happens after the previous errors as well).