From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chip Coldwell Newsgroups: gmane.emacs.devel Subject: Re: 22.0.99 emacs dumper (?) problem Date: Fri, 18 May 2007 12:19:17 -0400 (EDT) Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: sea.gmane.org 1179505182 2293 80.91.229.12 (18 May 2007 16:19:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 18 May 2007 16:19:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Neal Becker Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 18 18:19:41 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 1Hp5B2-00045G-Na for ged-emacs-devel@m.gmane.org; Fri, 18 May 2007 18:19:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hp5JG-0000mU-5m for ged-emacs-devel@m.gmane.org; Fri, 18 May 2007 12:28:06 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hp5JC-0000mF-3N for emacs-devel@gnu.org; Fri, 18 May 2007 12:28:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hp5JA-0000m3-Dn for emacs-devel@gnu.org; Fri, 18 May 2007 12:28:01 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hp5JA-0000m0-93 for emacs-devel@gnu.org; Fri, 18 May 2007 12:28:00 -0400 Original-Received: from mx1.redhat.com ([66.187.233.31]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hp5At-0003tZ-Sp for emacs-devel@gnu.org; Fri, 18 May 2007 12:19:28 -0400 Original-Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l4IGJIhF025081; Fri, 18 May 2007 12:19:18 -0400 Original-Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4IGJHOA010942; Fri, 18 May 2007 12:19:18 -0400 Original-Received: from vpn-248-102.boston.redhat.com (vpn-248-102.boston.redhat.com [10.13.248.102]) by mail.boston.redhat.com (8.13.1/8.13.1) with ESMTP id l4IGJHZn024014; Fri, 18 May 2007 12:19:17 -0400 In-Reply-To: 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:71324 Archived-At: 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. Chip -- Charles M. "Chip" Coldwell Senior Software Engineer Red Hat, Inc 978-392-2426