From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7390 invoked by alias); 4 Oct 2002 17:26:21 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7151 invoked from network); 4 Oct 2002 17:25:50 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 4 Oct 2002 17:25:50 -0000 Received: from node1.ott.qnx.com (node1.ott.qnx.com [192.168.163.104]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id NAA32054 for ; Fri, 4 Oct 2002 13:29:17 -0400 Received: (from alain@localhost) by node1.ott.qnx.com (8.8.8/8.6.12) id NAA24260 for gdb-patches@sources.redhat.com; Fri, 4 Oct 2002 13:25:07 -0400 Message-Id: <200210041725.NAA24260@node1.ott.qnx.com> Subject: Re: Patch for gdb/mi problem 702 To: keiths@redhat.com (Keith Seitz) Date: Fri, 04 Oct 2002 10:26:00 -0000 From: "Alain Magloire" Cc: jjohnstn@redhat.com (J. Johnston), gdb-patches@sources.redhat.com In-Reply-To: from "Keith Seitz" at Oct 04, 2002 10:15:20 AM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-10/txt/msg00131.txt.bz2 > > On Fri, 4 Oct 2002, J. Johnston wrote: > > > Some of these output variables are aliases of one another > > (e.g. *p which points to a[5] which is also being shown). The application > > kicks off a separate input field operation that changes the value of a[5]. > > Now, the application knows it changed a[5], but doesn't necessarily know about > > the current alias to *p. > > You'll also get a target_changed event. This will cause the UI to run > -var-update, which will show that the "aliased" object's value has > changed. This already works in insight. > Yes, as J. Johnston was saying, it was more in the case: you write to a memory, the memory is actually pointing to some variables. You would want the change events for the variables affected also, We do actually send the ChangeEvent on behalf of gdb in eclipse, but we do not know of the side-effects. The target_changed does not specify who is affected, which force a cascade of -var-evaluate-expression of all the objects. And I beleive this will only be in gdb-5.4 and up(can not wait to start to work on it to take advantage of the improve MI2 8-).