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: Tue, 7 Dec 2004 21:46:04 +0100 Message-ID: <030A00E8-4891-11D9-B72C-000D93505B76@swipnet.se> References: <87k6rvvybw.fsf_-_@jurta.org> <200412071754.06950.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 1102452473 4337 80.91.229.6 (7 Dec 2004 20:47:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 7 Dec 2004 20:47:53 +0000 (UTC) Cc: emacs-devel@gnu.org, "Kim F. Storm" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 07 21:47:39 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 1CbmFG-0007mx-00 for ; Tue, 07 Dec 2004 21:47:38 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbmP4-0005kN-ES for ged-emacs-devel@m.gmane.org; Tue, 07 Dec 2004 15:57:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CbmOm-0005kI-Ha for emacs-devel@gnu.org; Tue, 07 Dec 2004 15:57:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CbmOl-0005jv-Ti for emacs-devel@gnu.org; Tue, 07 Dec 2004 15:57:28 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbmOl-0005js-QT for emacs-devel@gnu.org; Tue, 07 Dec 2004 15:57:27 -0500 Original-Received: from [195.54.107.73] (helo=mxfep02.bredband.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CbmE8-00015s-1y for emacs-devel@gnu.org; Tue, 07 Dec 2004 15:46:28 -0500 Original-Received: from coolsville.localdomain ([83.226.180.210] [83.226.180.210]) by mxfep02.bredband.com with ESMTP id <20041207204627.LAWC6820.mxfep02.bredband.com@coolsville.localdomain>; Tue, 7 Dec 2004 21:46:27 +0100 In-Reply-To: <200412071754.06950.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:30812 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30812 2004-12-07 kl. 16.54 skrev Paul Pogonyshev: > Kim F. Storm wrote: >> Please do -- I know there is a memory corruption issue somewhere but >> so far nobody's been able to identify under what circumstances they >> happen. > > Somebody with a very fast machine with lots of RAM and lots of spare > time could try to run Emacs under Valgrind. From Valgrind documentation: 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. Jan D.