unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: emacs-devel@gnu.org
Subject: Re: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs	segfault
Date: Fri, 20 Apr 2012 17:15:18 +0300	[thread overview]
Message-ID: <83397yij61.fsf@gnu.org> (raw)
In-Reply-To: <87ty0ek49j.fsf@rho.meyering.net>

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



  reply	other threads:[~2012-04-20 14:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2012-04-20 15:46         ` Jim Meyering

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=83397yij61.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).