From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Jan D." Newsgroups: gmane.emacs.devel Subject: Re: GC crashes Date: Wed, 8 Dec 2004 07:04:15 +0100 Message-ID: References: <200412071754.06950.pogonyshev@gmx.net> <16822.6213.912468.936725@farnswood.snap.net.nz> <200412080217.55955.pogonyshev@gmx.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1102485923 12193 80.91.229.6 (8 Dec 2004 06:05:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2004 06:05:23 +0000 (UTC) Cc: Nick Roberts , emacs-devel@gnu.org, "Kim F. Storm" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 08 07:05:18 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Cbuww-0000ua-00 for ; Wed, 08 Dec 2004 07:05:18 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cbv6l-0004Y5-Sq for ged-emacs-devel@m.gmane.org; Wed, 08 Dec 2004 01:15:27 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Cbv6J-0004Xh-P5 for emacs-devel@gnu.org; Wed, 08 Dec 2004 01:14:59 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Cbv6J-0004XJ-0v for emacs-devel@gnu.org; Wed, 08 Dec 2004 01:14:59 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cbv6I-0004XG-ST for emacs-devel@gnu.org; Wed, 08 Dec 2004 01:14:58 -0500 Original-Received: from [195.54.107.73] (helo=mxfep02.bredband.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cbuw7-0000QK-Dh for emacs-devel@gnu.org; Wed, 08 Dec 2004 01:04:27 -0500 Original-Received: from coolsville.localdomain ([83.226.180.210] [83.226.180.210]) by mxfep02.bredband.com with ESMTP id <20041208060426.PEHL6820.mxfep02.bredband.com@coolsville.localdomain>; Wed, 8 Dec 2004 07:04:26 +0100 In-Reply-To: <200412080217.55955.pogonyshev@gmx.net> Original-To: Paul Pogonyshev X-Mailer: Apple Mail (2.619) 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: main.gmane.org gmane.emacs.devel:30849 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30849 >> Programs which are known not to work are: >> * emacs starts up but immediately concludes it is out of memory >> and >> aborts. Emacs has it's own memory-management scheme, but I >> don't >> understand why this should interact so badly with Valgrind. >> Emacs >> works fine if you build it to use the standard malloc/free >> routines. > > Then maybe someone should build it to use the standard malloc/free > routines > and try? (Yes, yes I should do it myself instead of bogging everybody > else, > but I don't have that much CPU time and I have not seen the infamous > memory > corruption yet, so I'm not that curious.) I just tried that, but it failed in the same way. Jan D.