GNU bug report logs - #25160
26.0.50; SIGSEGV when reading undo-tree file

Previous Next

Package: emacs;

Reported by: Pedro Silva <psilva <at> pedrosilva.pt>

Date: Sat, 10 Dec 2016 17:35:02 UTC

Severity: normal

Tags: confirmed, moreinfo

Merged with 27779

Found in version 26.0.50

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pedro Silva <psilva <at> pedrosilva.pt>
Cc: 25160 <at> debbugs.gnu.org
Subject: bug#25160: 26.0.50; SIGSEGV when reading undo-tree file
Date: Mon, 12 Dec 2016 18:11:03 +0200
> From: Pedro Silva <psilva <at> pedrosilva.pt>
> Cc: 25160 <at> debbugs.gnu.org
> Date: Mon, 12 Dec 2016 09:06:56 +0100
> 
> git-bisect tells me that this commit
> 
>     commit 07efb140348b4a4015c69ed102a5fa216978506f
>     Author: Tom Tromey <tromey <at> redhat.com>
>     Date:   Tue Aug 27 12:54:38 2013 -0600
> 
>         remove binding_symbol
> 
> is the culprit. However, after inspecting it, I confess I am not sure
> how. Most likely, I tagged something as bad or good where I shouldn't
> have. As the bisecting got me further away from HEAD and into a fairly
> deep branch, building cleanly got more and more difficult, and I
> couldn't actually replicate the crash anymore.
> 
> I will try to replicate this more thoroughly next weekend. I'll need to
> come up with a robust way to build so that I can actually automate the
> bisecting with `run'.

If it's clear that this is caused by the concurrency merge (which you
could verify by building a tree before commit 2412a1f), then you don't
need to look into the branch that got merged by that commit.

Thank you for your efforts.




This bug report was last modified 3 years and 29 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.