From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: stephane chatigny Newsgroups: gmane.lisp.guile.user Subject: Re: potential memory leak in do loop Date: Thu, 04 May 2006 10:41:18 -0400 Message-ID: References: <390990895AACCE4AA76C5A19872C8ADB233D6C@serveur0.coractive.local> <87iron98uf.fsf@zip.com.au> <4458B106.3030109@coractive.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1146753734 26543 80.91.229.2 (4 May 2006 14:42:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 4 May 2006 14:42:14 +0000 (UTC) Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Thu May 04 16:42:08 2006 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Fbf1f-0003xp-RH for guile-user@m.gmane.org; Thu, 04 May 2006 16:41:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fbf1f-0006Zt-8M for guile-user@m.gmane.org; Thu, 04 May 2006 10:41:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fbf1b-0006ZI-EY for guile-user@gnu.org; Thu, 04 May 2006 10:41:51 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fbf1a-0006Z6-Rs for guile-user@gnu.org; Thu, 04 May 2006 10:41:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fbf1a-0006Z3-Oy for guile-user@gnu.org; Thu, 04 May 2006 10:41:50 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fbf2D-0001TY-DW for guile-user@gnu.org; Thu, 04 May 2006 10:42:29 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Fbf1O-0003tl-4T for guile-user@gnu.org; Thu, 04 May 2006 16:41:38 +0200 Original-Received: from c207.134.68-2.clta.globetrotter.net ([207.134.68.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 May 2006 16:41:38 +0200 Original-Received: from stephane.chatigny by c207.134.68-2.clta.globetrotter.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 May 2006 16:41:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: guile-user@gnu.org Original-Lines: 60 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: c207.134.68-2.clta.globetrotter.net User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) In-Reply-To: <4458B106.3030109@coractive.com> X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:5286 Archived-At: Thanks Kevin and Paul, I am little bit rusty with Linux. I have not used it since my graduate studies ten years ago. I was not aware of the "top" command. I will monitor the process with it. Right now the memory usage seems fairly constant at 30Mb. If I need to use some kind of debuging package, I guess that I will need at least to recompile "mpb" with the proper debugging flag. That will help to see if the problems comes from mpb. Do I have also to recompile "Guile" with the debuging flags on? thanks Stef stephane chatigny a écrit : > Thanks Kevin, > > Does a Unix command like "pmap PID" could help me to determine if there > is a memory leak in the process? > > I have run the program for 24hrs and the memory usage seems to be > constant at ~28-30Mb. It usually takes 36hrs to generate the bug, I will > wait and see if the memory usage remains constant. > > regards > Stef > > > > > Kevin Ryde a écrit : >> Stephane Chatigny writes: >>> (although I have not tracked the memory usage yet). >> >> You'll probably have to use one of the various malloc debugging >> packages to find who has allocated the memory that's never freed, to >> see who's supposed to be responsible for that. >> >> >> _______________________________________________ >> Guile-user mailing list >> Guile-user@gnu.org >> http://lists.gnu.org/mailman/listinfo/guile-user >> > > > > > _______________________________________________ > Guile-user mailing list > Guile-user@gnu.org > http://lists.gnu.org/mailman/listinfo/guile-user > _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user