From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Memory leaks Date: Tue, 08 Mar 2011 19:40:33 -0500 Message-ID: References: <4D70CF59.4010406@cs.bham.ac.uk> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: dough.gmane.org 1299631464 31795 80.91.229.12 (9 Mar 2011 00:44:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 9 Mar 2011 00:44:24 +0000 (UTC) Cc: u.s.reddy@cs.bham.ac.uk, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 09 01:44:20 2011 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.69) (envelope-from ) id 1Px7Vj-0003vg-LQ for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2011 01:44:19 +0100 Original-Received: from localhost ([127.0.0.1]:57513 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Px7Vj-00088f-4v for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2011 19:44:19 -0500 Original-Received: from [140.186.70.92] (port=50666 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Px7S8-0005ho-Cb for emacs-devel@gnu.org; Tue, 08 Mar 2011 19:40:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Px7S7-000215-Cm for emacs-devel@gnu.org; Tue, 08 Mar 2011 19:40:36 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:33246) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Px7S7-00020x-5S for emacs-devel@gnu.org; Tue, 08 Mar 2011 19:40:35 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Px7S5-0003L3-U9; Tue, 08 Mar 2011 19:40:33 -0500 In-reply-to: (message from Andreas Schwab on Tue, 08 Mar 2011 09:57:11 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 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:136930 Archived-At: Is it possible to write code to record which vectors were consed by the operation suspected of having a memory leak? Then a function to call from GDB to test whether a vector are still alive. After you find one, you could do a GC with a conditional breakpoint to stop when that vector is marked. Then you would see exactly what is keeping it alive. If you do this for each vector that was consed during the operation in question, you will eventually find one that was expected to be GC'd, and find the bug. -- Dr Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org, www.gnu.org