From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Neal Becker Newsgroups: gmane.emacs.devel Subject: Re: 22.0.99 emacs dumper (?) problem Date: Fri, 18 May 2007 19:00:29 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: sea.gmane.org 1179529272 1649 80.91.229.12 (18 May 2007 23:01:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 18 May 2007 23:01:12 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 19 01:01:09 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HpBRa-0001MH-2i for ged-emacs-devel@m.gmane.org; Sat, 19 May 2007 01:01:06 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HpBRZ-0000w3-Nr for ged-emacs-devel@m.gmane.org; Fri, 18 May 2007 19:01:05 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HpBRX-0000vQ-16 for emacs-devel@gnu.org; Fri, 18 May 2007 19:01:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HpBRT-0000ue-04 for emacs-devel@gnu.org; Fri, 18 May 2007 19:01:02 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HpBRS-0000uZ-Ob for emacs-devel@gnu.org; Fri, 18 May 2007 19:00:58 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HpBRS-0005jy-8A for emacs-devel@gnu.org; Fri, 18 May 2007 19:00:58 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HpBRE-0007oV-Ju for emacs-devel@gnu.org; Sat, 19 May 2007 01:00:44 +0200 Original-Received: from pool-70-16-175-83.hag.east.verizon.net ([70.16.175.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 19 May 2007 01:00:44 +0200 Original-Received: from ndbecker2 by pool-70-16-175-83.hag.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 19 May 2007 01:00:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 53 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: pool-70-16-175-83.hag.east.verizon.net User-Agent: KNode/0.10.4 X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:71352 Archived-At: Chip Coldwell wrote: > On Fri, 18 May 2007, Neal Becker wrote: > >> Chip Coldwell wrote: >> >> > >> > 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 >> > >> >> This worked for me with emacs-23.0.0.1 until yesterday's update to >> glibc-2.6-1. (No, I haven't rebuilt emacs today after the glibc-2.6-1 >> update) > > Do you mean that dumping emacs-23.0.0.1 with "MALLOC_MMAP_MAX_=0" > built a binary that worked with glibc-2.5.90-22 but stopped working > after the update to glibc-2.6-1? > > emacs-23 is the unicode2 branch, right? I would assume that the > malloc hooks, dumper, lisp allocator, etc are common to the two > branches. > Yes. What's strange is, I did rebuild again with glibc-2.6-1, and now it's working again. Very strange.