From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18901 invoked by alias); 20 Jul 2009 13:27:04 -0000 Received: (qmail 18885 invoked by uid 22791); 20 Jul 2009 13:27:03 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Jul 2009 13:26:55 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id A94B0109FE; Mon, 20 Jul 2009 13:26:52 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 83773108CF; Mon, 20 Jul 2009 13:26:52 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MSstG-0000Xz-Q2; Mon, 20 Jul 2009 09:26:50 -0400 Date: Mon, 20 Jul 2009 13:34:00 -0000 From: Daniel Jacobowitz To: Thiago Jung Bauermann Cc: gdb-patches@sourceware.org, Tom Tromey , Vladimir Prus Subject: Re: Value reference counting Message-ID: <20090720132650.GA1875@caradoc.them.org> Mail-Followup-To: Thiago Jung Bauermann , gdb-patches@sourceware.org, Tom Tromey , Vladimir Prus References: <20090717184152.GA6863@caradoc.them.org> <20090717190418.GA9041@caradoc.them.org> <200907201022.19758.thiago.bauermann@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200907201022.19758.thiago.bauermann@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00473.txt.bz2 On Mon, Jul 20, 2009 at 10:22:19AM -0300, Thiago Jung Bauermann wrote: > Watchpoints hold their own references to values. Other than that, IMHO if > watchpoint code causes values to be leaked, that is a bug, not a special > feature which should be respected... WDYT? Confused by your question :-) The way free_all_values works is that it's only run after a command. For instance, a breakpoint command, or a user-typed command. It's not run every time we stop the target and do some thinking if the thinking is not in the form of a command. So it's possible to get values created that don't get cleaned up for a while. Leaked was probably not the right word, just not GC'd promptly. -- Daniel Jacobowitz CodeSourcery