Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault

[Jim Meyering]

Eli Zaretskii wrote:
>> From: Jim Meyering <address@hidden>
>> Date: Fri, 20 Apr 2012 13:54:16 +0200
>>
>> Jim Meyering wrote:
>>
>> > Jim Meyering wrote:
>> >> Jim Meyering wrote:
>> >>> Just a heads-up, since release is so near:
>> >>>
>> >>>     gcc-4.8.0 vs emacs+MALLOC_PERTURB_ = ./temacs segfault
>> >>>     http://debbugs.gnu.org/11144
>> >>>
>> >>> It would be a shame if gcc-4.8.0 (even test a release) were to
>> >>> fail to bootstrap emacs with MALLOC_PERTURB_ set to nonzero.
>> >>
>> >> This seems to have been fixed, since with the latest from gcc/svn,
>> >>   git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/address@hidden
>> >> 138bc75d-0d04-0410-961f-82ee72b054a4
>> >> I can now bootstrap the latest emacs.
>> >
>> > This has struck again, now using gcc version 4.8.0 20120406
>> > I've reopened the bug.
>>
>> While I filed in a new bug, the patch in bug#11288 may well
>> solve the above, too:
>>
>>     avoid buffer overrun in display code
>>     http://bugs.gnu.org/11288
>
> Please see if revision 107873 on the emacs-24 branch, which should
> solve the overrun, solves also the bootstrap problem.  (Personally, I
> doubt that, because display code is not invoked during bootstrap.  But
> then who knows?)

I don't have a reliable reproducer for that one.
I typically bootstrap the latest emacs using the latest gcc, once or
twice a day.  If I go a couple weeks without hitting the above bug,
I'll start to wonder if it's been resolved.

Today it has not been triggered, neither before nor after your change.
The last time I saw it was when building on April 17th.