all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 18:15:40 +0200	[thread overview]
Message-ID: <83a8q3z843.fsf@gnu.org> (raw)
In-Reply-To: <87y4domo6i.fsf@web.de>

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 21982@debbugs.gnu.org
> Date: Mon, 23 Nov 2015 21:54:45 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Was your branch tree created by "git worktree"?
> 
> I never used that command, so I guess "no".

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.)

Btw, the problem with "End of file during parsing" I reported came
back today: I again got null bytes in the middle of the file.  So
whatever was causing corruption of loaddefs.el is still with us.

Thanks.





  reply	other threads:[~2015-11-24 16:15 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 [this message]
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=83a8q3z843.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.