From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: 22.0.99 emacs dumper (?) problem Date: Mon, 21 May 2007 09:24:34 -0400 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1179753964 17922 80.91.229.12 (21 May 2007 13:26:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 21 May 2007 13:26:04 +0000 (UTC) Cc: coldwell@redhat.com, emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 21 15:26:01 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 1Hq7td-0000ZK-EK for ged-emacs-devel@m.gmane.org; Mon, 21 May 2007 15:25:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hq7tc-0001nb-Uf for ged-emacs-devel@m.gmane.org; Mon, 21 May 2007 09:25:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hq7sO-0000Gi-FP for emacs-devel@gnu.org; Mon, 21 May 2007 09:24:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hq7sN-0000GA-DD for emacs-devel@gnu.org; Mon, 21 May 2007 09:24:39 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hq7sN-0000G2-5W for emacs-devel@gnu.org; Mon, 21 May 2007 09:24:39 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hq7sM-0005Hg-8o for emacs-devel@gnu.org; Mon, 21 May 2007 09:24:38 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1Hq7sI-0000p6-3a; Mon, 21 May 2007 09:24:34 -0400 In-reply-to: (message from Chong Yidong on 20 May 2007 23:26:46 -0400) 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:71504 Archived-At: I cannot reconcile the things that you've said about the problem. If this is the full extent of the problem 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. then it ought to work just to relink temacs with the newer libc and then dump Emacs again. (Mr Coldwell, what happens if you do that?) However, if this change is needed also + MALLOC_MMAP_MAX_=0 LC_ALL=C $(RUN_TEMACS) -nl -batch -l loadup dump to make Emacs work with the newer libc, it implies there is a worse problem. It implies that Emacs fails to work correctly with the newer libc, and never mind what the older libc did. Which is it? Meanwhile, is this workaround really ok? That depends on facts I don't know. Maybe it only prevents use of mmap while dumping. That is not a big price to pay. But maybe it also prevents use of mmap when the dumped Emacs is subsequently run. That could be a high price to pay. Can Mr Coldwell (or anyone) tell us which? If it only prevents use of mmap when running temacs, then it is ok as a workaround, but I would like to generate it automatically thru the makefile mechanism rather than ask users to patch it by hand.