From: Chong Yidong <cyd@MIT.EDU>
To: Chip Coldwell <coldwell@redhat.com>
Cc: emacs-devel@gnu.org
Subject: Re: 22.0.99 emacs dumper (?) problem
Date: 20 May 2007 23:26:46 -0400 [thread overview]
Message-ID: <unusl9q3lhl.fsf@all-night-tool.mit.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0705180936190.3221@localhost.localdomain>
> an emacs binary built using the Fedora 7 build system will seg-fault
> immediately when run on a Fedora 7 install. The stack trace shows
> an assert failing in the glibc malloc code (usually it's setlocale
> invoking malloc); it appears that something about the way the dumper
> preserves the malloc state between the dumping emacs and the dumped
> emacs isn't quite working.
>From reading the bugzilla entry, it appears that the problem is a set
of bugs in glibc that are exposed by the way Emacs uses
malloc_set_state. Changing Emacs to avoid this, even if it's
possible, will probably delay the Emacs 22.1 release by another year
or so, which is undesirable.
Therefore, I propose adding the following entry to the Emacs PROBLEMS
file.
** Emacs crashes on startup on Fedora Core 7.
This appears to be due to a change in the internal format of freed
blocks introduced between glibc-2.5.90-21 and glibc-2.5.90-22. As a
result, Emacs binaries built using older versions of glibc may crash
when run using newer versions of glibc. For details, see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239344
Rebuilding Emacs with newer versions of glibc, with the following
patch applied to the Emacs source tree, should remove the crashes.
--- emacs-22.0.95/src/Makefile.in-save 2007-05-13 11:53:01.000000000 -0700
+++ emacs-22.0.95/src/Makefile.in 2007-05-13 11:53:55.000000000 -0700
@@ -960,7 +960,7 @@
ln temacs${EXEEXT} emacs${EXEEXT}
#else
#ifdef HAVE_SHM
- LC_ALL=C $(RUN_TEMACS) -nl -batch -l loadup dump
+ MALLOC_MMAP_MAX_=0 LC_ALL=C $(RUN_TEMACS) -nl -batch -l loadup dump
#else /* ! defined (HAVE_SHM) */
LC_ALL=C $(RUN_TEMACS) -batch -l loadup dump
#endif /* ! defined (HAVE_SHM) */
Are there any objections?
next prev parent reply other threads:[~2007-05-21 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:42 22.0.99 emacs dumper (?) problem Chip Coldwell
2007-05-18 14:16 ` Neal Becker
2007-05-18 16:19 ` Chip Coldwell
2007-05-18 23:00 ` Neal Becker
2007-05-19 22:32 ` Richard Stallman
2007-05-21 3:26 ` Chong Yidong [this message]
2007-05-21 7:49 ` Glenn Morris
2007-05-21 13:24 ` Richard Stallman
2007-05-21 14:45 ` Chip Coldwell
2007-05-21 14:47 ` Chip Coldwell
2007-05-21 15:27 ` Chong Yidong
2007-05-21 15:28 ` Chip Coldwell
2007-05-22 14:51 ` Richard Stallman
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=unusl9q3lhl.fsf@all-night-tool.mit.edu \
--to=cyd@mit.edu \
--cc=coldwell@redhat.com \
--cc=emacs-devel@gnu.org \
/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).