From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21868 invoked by alias); 12 Jan 2008 03:49:23 -0000 Received: (qmail 21859 invoked by uid 22791); 12 Jan 2008 03:49:23 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 12 Jan 2008 03:49:03 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id B00A49811D; Sat, 12 Jan 2008 03:49:01 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 83B6098100; Sat, 12 Jan 2008 03:49:01 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JDXMi-0002Oy-3D; Fri, 11 Jan 2008 22:49:00 -0500 Date: Sat, 12 Jan 2008 03:49:00 -0000 From: Daniel Jacobowitz To: Marc Khouzam Cc: gdb@sources.redhat.com Subject: Re: -var-update using formatted value Message-ID: <20080112034900.GA8947@caradoc.them.org> Mail-Followup-To: Marc Khouzam , gdb@sources.redhat.com References: <6D19CA8D71C89C43A057926FE0D4ADAA04290E1B@ecamlmw720.eamcs.ericsson.se> <18311.60638.724524.220449@kahikatea.snap.net.nz> <20080111225928.GA26360@caradoc.them.org> <18311.65093.38930.103045@kahikatea.snap.net.nz> <20080111235219.GA29698@caradoc.them.org> <6D19CA8D71C89C43A057926FE0D4ADAA2DE08B@ecamlmw720.eamcs.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA2DE08B@ecamlmw720.eamcs.ericsson.se> User-Agent: Mutt/1.5.17 (2007-12-11) 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/msg00083.txt.bz2 On Fri, Jan 11, 2008 at 10:41:19PM -0500, Marc Khouzam wrote: > For example, in your example of strings changing from > natural value: 0x804a018 "GNU" to > natural value: 0x804a018 "GDB" > If the variable object tracking this has its format set to anything else than natural, > the actual string is not printed and the value seems to stay the same so > -var-update will not detect the change in value. That is deliberate. I reread your message, and I still can't see a good reason for -var-update to report a changed variable if -var-evaluate-expression is going to continue to display it the same way, i.e. as if no update has occurred. If you're worried about multiple formats, maybe you should keep a varobj for each instead of switching one around? -- Daniel Jacobowitz CodeSourcery