From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: unexec problem Date: Sun, 10 Feb 2008 21:58:59 +0200 Message-ID: References: <878x20v2ki.fsf@stupidchicken.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1202673568 5970 80.91.229.12 (10 Feb 2008 19:59:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 10 Feb 2008 19:59:28 +0000 (UTC) Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 10 20:59:51 2008 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 1JOIL8-0007Xu-DH for ged-emacs-devel@m.gmane.org; Sun, 10 Feb 2008 20:59:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOIKf-0005h9-5s for ged-emacs-devel@m.gmane.org; Sun, 10 Feb 2008 14:59:21 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JOIKb-0005fr-1o for emacs-devel@gnu.org; Sun, 10 Feb 2008 14:59:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JOIKa-0005ea-CF for emacs-devel@gnu.org; Sun, 10 Feb 2008 14:59:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOIKa-0005eG-6T for emacs-devel@gnu.org; Sun, 10 Feb 2008 14:59:16 -0500 Original-Received: from romy.inter.net.il ([213.8.233.24]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JOIKW-0002ZR-Gf; Sun, 10 Feb 2008 14:59:12 -0500 Original-Received: from HOME-C4E4A596F7 ([81.5.33.57]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id KEK68723 (AUTH halo1); Sun, 10 Feb 2008 21:58:37 +0200 (IST) In-reply-to: (message from Richard Stallman on Sun, 10 Feb 2008 13:42:09 -0500) X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) 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:88661 Archived-At: > From: Richard Stallman > CC: emacs-devel@gnu.org > Date: Sun, 10 Feb 2008 13:42:09 -0500 > > The idea was that maybe some library function we are now calling, and > that calls malloc internally, causes the corruption of the memory > allocation in the dumped Emacs. I don't know how to spot such a > function except by the method I suggested. > > The problem is how to find a candidate for the problem out of > thousands of backtraces of malloc calls. Does the dumped Emacs crash even if you dump it immediately after temacs starts, without loading any of the Lisp files it loads during loading loadup.el (by hacking it to comment out all the load commands)? If so, perhaps the amount of calls to malloc would be much smaller, and you could look at it.