From: Eli Zaretskii <eliz@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu
Subject: Re: compilation failure
Date: Wed, 30 Mar 2011 07:35:55 -0400 [thread overview]
Message-ID: <E1Q4tgp-0007cI-Ff@fencepost.gnu.org> (raw)
In-Reply-To: <87aagduk99.fsf@rho.meyering.net> (message from Jim Meyering on Wed, 30 Mar 2011 09:42:42 +0200)
> From: Jim Meyering <jim@meyering.net>
> Date: Wed, 30 Mar 2011 09:42:42 +0200
> Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
>
> This command,
> env MALLOC_PERTURB_=0 MALLOC_CHECK_=0 make -j9 bootstrap
> has succeeded for me on each of the last three mornings (Mar 28-30).
>
> I manually set those two MALLOC_*_ variables to 0 because
> when I don't, emacs fails to bootstrap.
It's a pity this problem was not reported to the bug tracker. (At
least I couldn't find it; apologies if I missed it.)
> I suspect that emacs is using free'd memory containing
> values that would normally be unoffensive, but when you set
> those envvars (esp MALLOC_PERTURB_) to nonzero, it makes
> glibc scribble on free'd buffers, and that makes emacs
> exhibit an actual failure.
Can you use bisect to find the guilty commit?
next prev parent reply other threads:[~2011-03-30 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 6:13 compilation failure Werner LEMBERG
2011-03-30 6:31 ` Paul Eggert
2011-03-30 6:52 ` Werner LEMBERG
2011-03-30 7:42 ` Jim Meyering
2011-03-30 8:04 ` Werner LEMBERG
2011-03-30 11:37 ` Eli Zaretskii
2011-03-30 12:29 ` Werner LEMBERG
2011-03-30 11:35 ` Eli Zaretskii [this message]
2011-03-30 13:41 ` Jim Meyering
2011-03-30 18:16 ` Eli Zaretskii
2011-03-30 18:16 ` Eli Zaretskii
2011-03-30 11:25 ` Eli Zaretskii
2011-03-30 13:00 ` Werner LEMBERG
2011-03-30 18:17 ` Eli Zaretskii
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=E1Q4tgp-0007cI-Ff@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
/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).