unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chip Coldwell <coldwell@redhat.com>
To: emacs-devel@gnu.org
Subject: 22.0.99 emacs dumper (?) problem
Date: Fri, 18 May 2007 09:42:19 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705180936190.3221@localhost.localdomain> (raw)


I would like to bring the bug described here:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239344

to the attention of this mailing list.  In a nutshell, what happens is
that 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.

Another theory that is being examined is that somewhere there is a
pointer to anonymous mmaped memory.  It seems that prepending

MALLOC_MMAP_MAX_=0

to this line

LC_ALL=C $(RUN_TEMACS) -nl -batch -l loadup dump

works, although there are some conflicting reports about this, also.

Anyway, if we could get some more eyes on this bug, it would probably
help a bunch.

Chip

-- 
Charles M. "Chip" Coldwell
Senior Software Engineer
Red Hat, Inc
978-392-2426

             reply	other threads:[~2007-05-18 13:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 13:42 Chip Coldwell [this message]
2007-05-18 14:16 ` 22.0.99 emacs dumper (?) problem 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
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=Pine.LNX.4.64.0705180936190.3221@localhost.localdomain \
    --to=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).