From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 21982@debbugs.gnu.org
Subject: bug#21982: 25.1.50; Building emacs-25 branch fails
Date: Tue, 24 Nov 2015 19:57:32 +0200 [thread overview]
Message-ID: <83vb8rxotv.fsf@gnu.org> (raw)
In-Reply-To: <878u5n5lwm.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 21982@debbugs.gnu.org
> Date: Tue, 24 Nov 2015 18:48:09 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can you run Emacs under valgrind? It should be able to find the
> > offending code. (I assume that just running by hand the single
> > command that aborts is sufficient to reproduce the problem.)
>
> I would first have to learn how to do that.
Perhaps Paul could help you.
> I did something different in the meantime. I bisected again, but with
> version.el fix from the first bad commit. This leaded to
>
> --8<---------------cut here---------------start------------->8---
> a4c6f55b9a222849a1c5d590589b1f8f0627d6f8 is the first bad commit
> commit a4c6f55b9a222849a1c5d590589b1f8f0627d6f8
> Author: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun Nov 15 07:00:45 2015 +0200
> Unify the absolutely equal xref-backend-references implementations
>
> * lisp/progmodes/elisp-mode.el (xref-backend-references):
> Remove.
>
> * lisp/progmodes/etags.el (xref-backend-references):
> Remove.
>
> * lisp/progmodes/xref.el (xref-backend-references):
> Define the default implementation.
> --8<---------------cut here---------------end--------------->8---
>
> So, this is the commit that caused the change in version.el to break
> Emacs. Dunno if this is the end of the chain.
>
> Is this information useful?
I don't see how this could be relevant. In particular, this commit
doesn't touch version.el. How could it cause a change in version.el?
What am I missing?
next prev parent reply other threads:[~2015-11-24 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 17:58 bug#21982: 25.1.50; Building emacs-25 branch fails Michael Heerdegen
2015-11-22 18:45 ` Eli Zaretskii
2015-11-23 10:36 ` Michael Heerdegen
2015-11-23 16:19 ` Eli Zaretskii
2015-11-23 20:35 ` Michael Heerdegen
2015-11-23 20:49 ` Eli Zaretskii
2015-11-23 20:54 ` Michael Heerdegen
2015-11-24 16:15 ` Eli Zaretskii
2015-11-24 17:48 ` Michael Heerdegen
2015-11-24 17:57 ` Eli Zaretskii [this message]
2015-11-25 17:58 ` Michael Heerdegen
2015-11-25 18:20 ` Eli Zaretskii
2017-01-29 23:22 ` npostavs
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=83vb8rxotv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21982@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).