From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20150 invoked by alias); 3 Jan 2005 00:49:51 -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 20101 invoked from network); 3 Jan 2005 00:49:42 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 3 Jan 2005 00:49:42 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1ClGPh-00082P-PB; Sun, 02 Jan 2005 19:49:37 -0500 Date: Mon, 03 Jan 2005 00:49:00 -0000 From: Daniel Jacobowitz To: Andreas Schwab Cc: gdb-patches@sources.redhat.com Subject: Re: Don't error out when variable not available Message-ID: <20050103004937.GA30858@nevyn.them.org> Mail-Followup-To: Andreas Schwab , gdb-patches@sources.redhat.com References: <20050102225745.GA28488@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2005-01/txt/msg00005.txt.bz2 On Mon, Jan 03, 2005 at 12:49:04AM +0100, Andreas Schwab wrote: > Daniel Jacobowitz writes: > > > How about reusing the LOC_OPTIMIZED_OUT handling to describe this case? > > I believe that will print "foo = ". > > LOC_OPTIMIZED_OUT is not a value, but a static property of a symbol. I > don't think it fits into the dynamic nature of unavailable values. However, we always handle it in the same case statements that handle LOC_COMPUTED, which is how we get into the dwarf2 expression evaluator anyway. -- Daniel Jacobowitz