* bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault
@ 2012-04-01 18:44 Jim Meyering
2012-04-03 16:27 ` Jim Meyering
0 siblings, 1 reply; 6+ messages in thread
From: Jim Meyering @ 2012-04-01 18:44 UTC (permalink / raw)
To: Emacs development discussions
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault
2012-04-01 18:44 bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault Jim Meyering
@ 2012-04-03 16:27 ` Jim Meyering
2012-04-10 9:13 ` Jim Meyering
0 siblings, 1 reply; 6+ messages in thread
From: Jim Meyering @ 2012-04-03 16:27 UTC (permalink / raw)
To: Emacs development discussions; +Cc: 11144-done
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/trunk@186106 138bc75d-0d04-0410-961f-82ee72b054a4
I can now bootstrap the latest emacs.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault
2012-04-03 16:27 ` Jim Meyering
@ 2012-04-10 9:13 ` Jim Meyering
2012-04-20 11:54 ` Jim Meyering
0 siblings, 1 reply; 6+ messages in thread
From: Jim Meyering @ 2012-04-10 9:13 UTC (permalink / raw)
To: Emacs development discussions; +Cc: 11144
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/trunk@186106
> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault
2012-04-10 9:13 ` Jim Meyering
@ 2012-04-20 11:54 ` Jim Meyering
2012-04-20 14:15 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Jim Meyering @ 2012-04-20 11:54 UTC (permalink / raw)
To: Emacs development discussions
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/trunk@186106
>> 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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault
2012-04-20 11:54 ` Jim Meyering
@ 2012-04-20 14:15 ` Eli Zaretskii
2012-04-20 15:46 ` Jim Meyering
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2012-04-20 14:15 UTC (permalink / raw)
To: Jim Meyering; +Cc: emacs-devel
> From: Jim Meyering <jim@meyering.net>
> 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/trunk@186106
> >> 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?)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault
2012-04-20 14:15 ` Eli Zaretskii
@ 2012-04-20 15:46 ` Jim Meyering
0 siblings, 0 replies; 6+ messages in thread
From: Jim Meyering @ 2012-04-20 15:46 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel
Eli Zaretskii wrote:
>> From: Jim Meyering <jim@meyering.net>
>> 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/trunk@186106
>> >> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-04-20 15:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-01 18:44 bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault Jim Meyering
2012-04-03 16:27 ` Jim Meyering
2012-04-10 9:13 ` Jim Meyering
2012-04-20 11:54 ` Jim Meyering
2012-04-20 14:15 ` Eli Zaretskii
2012-04-20 15:46 ` Jim Meyering
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).