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: Mon, 23 Nov 2015 22:49:24 +0200 [thread overview]
Message-ID: <83mvu4zbjf.fsf@gnu.org> (raw)
In-Reply-To: <8737vw313t.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 21982@debbugs.gnu.org
> Date: Mon, 23 Nov 2015 21:35:50 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > If the abort is reproducible, by all means please do, and thanks.
>
> git bisect says that:
>
> --8<---------------cut here---------------start------------->8---
> c210b8b128c17929dbb8e0b0564ee25930d44dd1 is the first bad commit
> commit c210b8b128c17929dbb8e0b0564ee25930d44dd1
> Author: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu Nov 19 21:32:43 2015 +0100
> Discover repository version in linked worktrees (bug#21930)
>
> * lisp/version.el (emacs-repository--version-git-1): Do not assume
> HEAD is at .git/HEAD, it can also be at .git/worktrees/<branch>/HEAD.
> (emacs-repository-get-version): Grok linked worktrees when EXTERNAL
> is nil too.
> --8<---------------cut here---------------end--------------->8---
>
> I verified that it is indeed bad and that the parent commit is good,
> whereby "good" means it builds successfully and "bad" means building
> fails.
>
> Does that help?
Well, sort of. Granted, no Lisp change can ever cause thrashing of
the malloc arena, so the above could only expose a bug that was
already there.
Was your branch tree created by "git worktree"?
next prev parent reply other threads:[~2015-11-23 20:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvu4zbjf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.