From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9583 invoked by alias); 1 Nov 2007 15:40:01 -0000 Received: (qmail 9558 invoked by uid 22791); 1 Nov 2007 15:40:00 -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; Thu, 01 Nov 2007 15:39:58 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id F13AE98103; Thu, 1 Nov 2007 15:39:56 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id AD416980A7; Thu, 1 Nov 2007 15:39:56 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1Inc9D-0005OE-Az; Thu, 01 Nov 2007 11:39:55 -0400 Date: Thu, 01 Nov 2007 15:40:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus Cc: Nick Roberts , gdb-patches@sources.redhat.com Subject: Re: [PATCH] MI: lvalues and variable_editable Message-ID: <20071101153955.GA20676@caradoc.them.org> Mail-Followup-To: Vladimir Prus , Nick Roberts , gdb-patches@sources.redhat.com References: <18210.27153.559569.601092@kahikatea.snap.net.nz> <200710311458.58112.ghost@cs.msu.su> <18217.23406.21406.920384@kahikatea.snap.net.nz> <200710312247.40840.ghost@cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710312247.40840.ghost@cs.msu.su> User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes 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 X-SW-Source: 2007-11/txt/msg00011.txt.bz2 On Wed, Oct 31, 2007 at 10:47:40PM +0300, Vladimir Prus wrote: > I'm not sure that's possible. If you create varobj for *foo, and foo changes > to point to inaccessible memory, then assignment to *foo will fail, but I > don't know any mechanism in gdb that will tell you that without actually > trying assignment. Yes, there is no way to be sure without trying to write. Which we shouldn't unless the user asked us to, of course. -- Daniel Jacobowitz CodeSourcery