From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31501 invoked by alias); 27 Oct 2010 17:31:01 -0000 Received: (qmail 31280 invoked by uid 22791); 27 Oct 2010 17:30:59 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 27 Oct 2010 17:30:55 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id B47A22BAC6D; Wed, 27 Oct 2010 13:30:53 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id fiCXrhTskVh8; Wed, 27 Oct 2010 13:30:53 -0400 (EDT) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by rock.gnat.com (Postfix) with ESMTP id 71F8B2BAC41; Wed, 27 Oct 2010 13:30:53 -0400 (EDT) Message-ID: <4CC861C4.2060307@adacore.com> Date: Wed, 27 Oct 2010 17:31:00 -0000 From: Robert Dewar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5 MIME-Version: 1.0 To: Eran Ifrah CC: Jan Kratochvil , gdb@sourceware.org Subject: Re: GDB/MI - var-update/create BUG References: <20101027170327.GA11455@host1.dyn.jankratochvil.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-10/txt/msg00110.txt.bz2 On 10/27/2010 1:17 PM, Eran Ifrah wrote: >> normally you want to track that _variable_, not that _name_. >> Anywhere you are. I agree with that viewpoint >> > Not really, thats depends on what you are trying to achieve - since > variable object were designed to ease the task of the IDE, then I > say this is incorrect (at least to me). In my case, I actually never > want to track 'variable object' I want to track 'expressions' in the > code. OK, but this seems quite bizarre to me, and I would not want GDB to do this by default