From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 990 invoked by alias); 29 Aug 2013 17:21:05 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 978 invoked by uid 89); 29 Aug 2013 17:21:05 -0000 Received: from mms3.broadcom.com (HELO mms3.broadcom.com) (216.31.210.19) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 29 Aug 2013 17:21:05 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RDNS_NONE autolearn=no version=3.3.2 X-HELO: mms3.broadcom.com Received: from [10.9.208.57] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Thu, 29 Aug 2013 10:10:39 -0700 X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF Received: from IRVEXCHSMTP3.corp.ad.broadcom.com (10.9.207.53) by IRVEXCHCAS08.corp.ad.broadcom.com (10.9.208.57) with Microsoft SMTP Server (TLS) id 14.1.438.0; Thu, 29 Aug 2013 10:20:55 -0700 Received: from mail-irva-13.broadcom.com (10.10.10.20) by IRVEXCHSMTP3.corp.ad.broadcom.com (10.9.207.53) with Microsoft SMTP Server id 14.1.438.0; Thu, 29 Aug 2013 10:20:55 -0700 Received: from [10.177.73.74] (unknown [10.177.73.74]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id 8983AF2D72 for ; Thu, 29 Aug 2013 10:20:55 -0700 (PDT) Message-ID: <521F82F6.70208@broadcom.com> Date: Thu, 29 Aug 2013 17:21:00 -0000 From: "Andrew Burgess" User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: gdb-patches@sourceware.org Subject: PING: Re: [RFC 00/12] Merge value optimized_out and unavailable References: <5208D1DF.1090201@broadcom.com> In-Reply-To: <5208D1DF.1090201@broadcom.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-08/txt/msg00881.txt.bz2 Ping! Thanks, Andrew On 12/08/2013 1:15 PM, Andrew Burgess wrote: > This patch set merges together how gdb handles values that are > optimized out and values that are unavailable. > > I think that in most cases gdb should not care why the contents of > a value are not fetch-able, it is only when we need to display > something to the user that we should have to figure out was this > optimized-out or unavailable? > > After this patch set there will be a single unified interface to ask > if a value is available (either fully, partially, or for a range of > bit/bytes), this will answer in terms of both optimized out and > unavailable state. > > A second method will fetch the set of flags for the value > optimized/unavailable, this will be used for printing the correct string. > > For the implementation I've moved away from the code we currently have > for supporting partially optimized out values and consolidated on the > unavailable vector. > > Currently within gdb there are places where we handle optimized out and > unavailable differently, resulting in different style of output, and there > are places where we handle one of optimized out or unavailable, but not the > other. After this patch set it should (I hope) be much harder for either > of these situations to arise. > > Looking forward to your feedback. > > Thanks, > Andrew > > > >