From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Paul Pogonyshev Newsgroups: gmane.emacs.devel Subject: Re: GC crashes Date: Wed, 8 Dec 2004 02:17:55 +0200 Message-ID: <200412080217.55955.pogonyshev@gmx.net> References: <200412071754.06950.pogonyshev@gmx.net> <16822.6213.912468.936725@farnswood.snap.net.nz> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1102464889 5671 80.91.229.6 (8 Dec 2004 00:14:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2004 00:14:49 +0000 (UTC) Cc: "Kim F. Storm" , "Jan D." , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 08 01:14:43 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 1CbpTf-0001mv-00 for ; Wed, 08 Dec 2004 01:14:43 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbpdT-00063t-LX for ged-emacs-devel@m.gmane.org; Tue, 07 Dec 2004 19:24:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Cbpcc-0005vQ-Ea for emacs-devel@gnu.org; Tue, 07 Dec 2004 19:23:59 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CbpcY-0005uH-En for emacs-devel@gnu.org; Tue, 07 Dec 2004 19:23:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbpcX-0005u7-QV for emacs-devel@gnu.org; Tue, 07 Dec 2004 19:23:54 -0500 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CbpSQ-0005A3-TE for emacs-devel@gnu.org; Tue, 07 Dec 2004 19:13:27 -0500 Original-Received: (qmail 20164 invoked by uid 65534); 8 Dec 2004 00:13:24 -0000 Original-Received: from unknown (EHLO localhost.localdomain) (195.50.12.114) by mail.gmx.net (mp013) with SMTP; 08 Dec 2004 01:13:24 +0100 X-Authenticated: #16844820 Original-To: Nick Roberts User-Agent: KMail/1.4.3 In-Reply-To: <16822.6213.912468.936725@farnswood.snap.net.nz> 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:30819 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30819 Nick Roberts wrote: > > > Please do -- I know there is a memory corruption issue somewhere b= ut > > > so far nobody's been able to identify under what circumstances the= y > > > happen. > > > > Somebody with a very fast machine with lots of RAM and lots of spare > > time could try to run Emacs under Valgrind. > > Have you actually tried this? No, it was just a random idea. > I can't get it to work with Emacs and the documentation says: > > doco> Emacs is known not to work with Valgrind because Emacs has its ow= n > doco> memory-management scheme. Emacs works fine if you build it using = the > doco> standard malloc/free routines. I didn't know this. > Recently I downloaded Valgrind 2.2.0, and this now works with temacs wh= ere > previously (2.0.0) it ended with a segmentation fault. > > This runs like a dog though, and you need either a supercomputer or a l= ot > of patience. Programs under Valgrind run horribly slowly, but nevertheless I consider Valgrind invaluable. Under Valgrind your chances of spotting memory corruption and the line it happens at go up like some 100 times (of cours= e it cannot notice if you write within allocated memory, but still to a wrong place.) Jan D. wrote: > From Valgrind documentation: > > Programs which are known not to work are: > * emacs starts up but immediately concludes it is out of memory an= d > aborts. Emacs has it's own memory-management scheme, but I don't > understand why this should interact so badly with Valgrind. Emac= s > 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 routin= es and try? (Yes, yes I should do it myself instead of bogging everybody el= se, but I don't have that much CPU time and I have not seen the infamous memo= ry corruption yet, so I'm not that curious.) Paul