From: Eli Zaretskii <eliz@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: 11144@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 [thread overview]
Message-ID: <8362d77ut5.fsf@gnu.org> (raw)
In-Reply-To: <87hawslzkm.fsf@rho.meyering.net>
> From: Jim Meyering <jim@meyering.net>
> Date: Tue, 10 Apr 2012 11:13:13 +0200
> Cc: 11144@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@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.
next prev parent reply other threads:[~2012-04-10 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pqbre1gq.fsf@rho.meyering.net>
2012-04-03 16:27 ` bug#11144: bootstrap w/gcc-4.8.0 + nonzero MALLOC_PERTURB_ -> ./temacs segfault Jim Meyering
[not found] ` <87zkas232w.fsf@rho.meyering.net>
2012-04-10 9:13 ` Jim Meyering
[not found] ` <87hawslzkm.fsf@rho.meyering.net>
2012-04-10 10:19 ` Eli Zaretskii [this message]
2012-04-10 11:07 ` Jim Meyering
2012-04-10 16:36 ` Paul Eggert
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=8362d77ut5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11144@debbugs.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).