GNU bug report logs - #11144
temacs segfaults w/MALLOC_PERTURB_!=0 when compiling with gcc-4.8.0

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Meyering <jim <at> meyering.net>
Cc: 11144 <at> debbugs.gnu.org
Subject: bug#11144: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs	segfault
Date: Tue, 10 Apr 2012 13:19:50 +0300

> From: Jim Meyering <jim <at> meyering.net>
> Date: Tue, 10 Apr 2012 11:13:13 +0200
> Cc: 11144 <at> debbugs.gnu.org
> 
> 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 <at> 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.

Why should we consider this an Emacs bug?  Is there any evidence that
it's not a GCC bug, especially since it is coming and going depending
on GCC commits, and that you are using unreleased version of GCC?

P.S.  Please don't CC emacs-devel on bug reports, it causes problems
with the bug tracker, which sometimes creates bogus new bugs.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.