From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12865 invoked by alias); 2 Apr 2008 20:12:09 -0000 Received: (qmail 12855 invoked by uid 22791); 2 Apr 2008 20:12:08 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 02 Apr 2008 20:11:50 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m32KBmFN024087; Wed, 2 Apr 2008 16:11:48 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m32KBm76025987; Wed, 2 Apr 2008 16:11:48 -0400 Received: from lindt.uglyboxes.com (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m32KBjT3030388; Wed, 2 Apr 2008 16:11:47 -0400 Message-ID: <47F3E7C7.506@redhat.com> Date: Wed, 02 Apr 2008 20:12:00 -0000 From: Keith Seitz User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Doug Graham CC: gds , insight@sources.redhat.com Subject: Re: Crashes when "balloons" enabled References: <47F27765.8040905@redhat.com> <20080402000132.GA6223@nortel.com> <47F3C040.7030802@redhat.com> <20080402174323.GD6223@nortel.com> <47F3C933.9080904@redhat.com> <20080402200543.GE6223@nortel.com> In-Reply-To: <20080402200543.GE6223@nortel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00020.txt.bz2 Doug Graham wrote: > But c_value_of_variable() has been rewritten in 6.8 (but not 6.7.1), > and it looks like this bug might have been fixed, perhaps inadvertantly: > > varobj.c:2247 > if (var->not_fetched && value_lazy (var->value)) > /* Frozen variable and no value yet. We don't > implicitly fetch the value. MI response will > use empty string for the value, which is OK. */ > return NULL; > > It doesn't call either of gdb_value_fetch_lazy() or common_val_print() > any more. Yeah, there has been some churn in varobj in gdb recently. I'll have to double-check this to make sure that it is still "safe" or whether I have to jump through (even more) hoops to make it safe again. Keith