From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16625 invoked by alias); 11 Jan 2008 18:31:01 -0000 Received: (qmail 16617 invoked by uid 22791); 11 Jan 2008 18:31:01 -0000 X-Spam-Check-By: sourceware.org Received: from imr2.ericy.com (HELO imr2.ericy.com) (198.24.6.3) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 11 Jan 2008 18:30:40 +0000 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m0BIUSLj018544 for ; Fri, 11 Jan 2008 12:30:38 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 Jan 2008 12:30:33 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Re: -var-update using formatted value Date: Fri, 11 Jan 2008 18:31:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04290E1B@ecamlmw720.eamcs.ericsson.se> In-Reply-To: A From: "Marc Khouzam" To: 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: 2008-01/txt/msg00071.txt.bz2 > Why do you need "is it really changed" query? I'm working on the Eclipse front-end to GDB for DSDP/DSF. It offers the ability to optionally show all formats of a variable object (= binary, decimal, etc) To do this, we use -var-set-format. And to avoid having to repeatedly quer= y GDB for all formatted values of a varObject, we buffer all of them in the frontend. We only quer= y for those values again if the varObject has changed. The problem is that when it is time to do a -var-update (when the program s= tops), the varObject may not be set to the same format as at the time of the previous var-update. And i= n that case, -var-update will indicate a change in the value, which will cause the front= -end to unnecessarily clear its value-cache, and ask GDB again for each value. What I originally thought was that -var-udpate will notify the front-end if= the value 'really' changed. But since it is not the case, to work around it, I do a var-set-format to n= atural before each var-update.=20=20 But it seems like a bit of a hack. I was trying to understand why the new behaviour for var-udpate, but I have= n't figured out why a front-end would benefit from having -var-update indicate that a variable object has changed if only its printed value is different but no= t its actual content. Thanks Marc