From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Silva <psilva@pedrosilva.pt>
Cc: 25160@debbugs.gnu.org
Subject: bug#25160: 26.0.50; SIGSEGV when reading undo-tree file
Date: Mon, 12 Dec 2016 18:11:03 +0200 [thread overview]
Message-ID: <83inqpcelk.fsf@gnu.org> (raw)
In-Reply-To: <87y3zlefkv.fsf@pedrosilva.pt> (message from Pedro Silva on Mon, 12 Dec 2016 09:06:56 +0100)
> From: Pedro Silva <psilva@pedrosilva.pt>
> Cc: 25160@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@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.
next prev parent reply other threads:[~2016-12-12 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 16:31 bug#25160: 26.0.50; SIGSEGV when reading undo-tree file Pedro Silva
2016-12-10 19:57 ` Eli Zaretskii
2016-12-11 9:18 ` Pedro Silva
2016-12-11 15:32 ` Eli Zaretskii
2016-12-12 8:06 ` Pedro Silva
2016-12-12 16:11 ` Eli Zaretskii [this message]
2016-12-15 16:26 ` Eli Zaretskii
2017-12-12 2:38 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83inqpcelk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25160@debbugs.gnu.org \
--cc=psilva@pedrosilva.pt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).