From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Fabrice Popineau Newsgroups: gmane.emacs.devel Subject: Re: Emacs trunk crash Date: Fri, 27 Mar 2015 11:41:10 +0100 Message-ID: References: <834mpevkao.fsf@gnu.org> <837fu8srym.fsf@gnu.org> <831tkfsp68.fsf@gnu.org> <83wq26pawf.fsf@gnu.org> <83k2y4olsg.fsf@gnu.org> <837fu2bwd3.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c1d9d27c0107051242c66a X-Trace: ger.gmane.org 1427452914 18265 80.91.229.3 (27 Mar 2015 10:41:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Mar 2015 10:41:54 +0000 (UTC) To: Eli Zaretskii , Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 27 11:41:49 2015 Return-path: Envelope-to: ged-emacs-devel@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 1YbRhq-0007xm-Jt for ged-emacs-devel@m.gmane.org; Fri, 27 Mar 2015 11:41:38 +0100 Original-Received: from localhost ([::1]:49372 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbRhp-00058c-VH for ged-emacs-devel@m.gmane.org; Fri, 27 Mar 2015 06:41:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41522) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbRhm-00056M-4d for emacs-devel@gnu.org; Fri, 27 Mar 2015 06:41:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YbRhl-0002O5-1Q for emacs-devel@gnu.org; Fri, 27 Mar 2015 06:41:34 -0400 Original-Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]:33452) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbRhj-0002No-ON; Fri, 27 Mar 2015 06:41:31 -0400 Original-Received: by oifl3 with SMTP id l3so72592876oif.0; Fri, 27 Mar 2015 03:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=m+WnafCh+0TH69J6V9EnlLWKDVbQqYeRrOAcZHmvcBI=; b=Xlme9eKfG97uEdtnVQrg3EGO19pXkwseTk0wii3t1ITroxSGIaXtdyaOZdX96sDcDZ 0/mU2gwL14gyhHBAPmFEZARkhDGWOHUVh+D7zyzasq+DVa3hWJAalpUSFbb7Rq8OmWqj iV0JYD0USPFVw6fvbYN2x6/eGO2MLV63MPfNhqJqxv4qyiqLq5g/5AmX+FoiKPc5E+9L 2dw/aD6yAGIUrupM/WSro5IvtRwoFHuVMGA1cBI7vHzdvAGkhdXVCcR4IU7iMBCPlNaM bwS1zWb6k45nR/oqBkNmHX2CgHzxL6Wp2zZRhAQVJWz9EwNZ2NS4SHz82MiOV4vhpoUn +2mQ== X-Received: by 10.182.46.129 with SMTP id v1mr14377745obm.22.1427452890708; Fri, 27 Mar 2015 03:41:30 -0700 (PDT) Original-Received: by 10.202.196.207 with HTTP; Fri, 27 Mar 2015 03:41:10 -0700 (PDT) In-Reply-To: <837fu2bwd3.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c06::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:184372 Archived-At: --001a11c1d9d27c0107051242c66a Content-Type: text/plain; charset=UTF-8 2015-03-27 10:52 GMT+01:00 Eli Zaretskii : > > From: Fabrice Popineau > > Date: Wed, 25 Mar 2015 23:16:45 +0100 > > > > 2015-03-25 21:38 GMT+01:00 Eli Zaretskii : > > > > Try the patch below. It solves the crash with the file you sent, but > > the question is: does it also solve your real-life use case? > > > > > > Great! If you have an explanation about what is happening there, it > would be > > great too. > > About my real life case : that was the actual file preventing emacs to > run > > because of the crash. > > In all the undo-tree history files, only this one had a dumped syntax > table. > > I have no idea why undo-tree wants to do that. > > But in any case, emacs shouldn't crash when reading data that it has > printed > > itself. > > Did you try the patch? Can I commit it? > Yes. You should commit it in my opinion. I don't know if something else needs to be patched, but reviving the same state that was crashing, emacs could start and I was able to undo stuff from the undo-tree-history. Thanks a lot for the patch. Fabrice --001a11c1d9d27c0107051242c66a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-03-27 10:52 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:
=
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Wed, 25 Mar 2015 23:16:45 +0100
>
> 2015-03-25 21:38 GMT+01:00 Eli Zaretskii= <eliz@gnu.org>:
>
>=C2=A0 =C2=A0 =C2=A0Try the patch below. It solves the crash with the f= ile you sent, but
>=C2=A0 =C2=A0 =C2=A0the question is: does it also solve your real-life = use case?
>
>
> Great! If you have an explanation about what is happening there, it wo= uld be
> great too.
> About my real life case : that was the actual file preventing emacs to= run
> because of the crash.
> In all the undo-tree history files, only this one had a dumped syntax = table.
> I have no idea why undo-tree wants to do that.
> But in any case, emacs shouldn't crash when reading data that it h= as printed
> itself.

Did you try the patch?=C2=A0 Can I commit it?


Yes. You should commit it in my opinion. I don't know= if something else needs to be patched, but reviving the same
state that was crashing, emacs could start and I was abl= e to undo stuff from the undo-tree-history.

Thanks a lot for the patch.

Fabrice
--001a11c1d9d27c0107051242c66a--