[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compilation failure
From: |
Eli Zaretskii |
Subject: |
Re: compilation failure |
Date: |
Wed, 30 Mar 2011 07:35:55 -0400 |
> From: Jim Meyering <address@hidden>
> Date: Wed, 30 Mar 2011 09:42:42 +0200
> Cc: address@hidden, address@hidden
>
> 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?