From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19221 invoked by alias); 2 Apr 2008 18:01:45 -0000 Received: (qmail 19169 invoked by uid 22791); 2 Apr 2008 18:01:37 -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 18:01:19 +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 m32I1H8a024025; Wed, 2 Apr 2008 14:01:18 -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 m32I1Hrv021795; Wed, 2 Apr 2008 14:01:17 -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 m32I1F6f023733; Wed, 2 Apr 2008 14:01:16 -0400 Message-ID: <47F3C933.9080904@redhat.com> Date: Wed, 02 Apr 2008 18:01: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> In-Reply-To: <20080402174323.GD6223@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/msg00016.txt.bz2 Doug Graham wrote: > #7 0x08175e79 in gdb_value_fetch_lazy (val=0x97e94e8) > at ../../insight-6.5/gdb/wrapper.c:64 This function is a call wrapper: it "wraps" the gdb call, value_fetch_lazy (which will longjmp) with a version which catches the exception and returns a value indicating success or failure: int gdb_value_fetch_lazy (struct value *val) { volatile struct gdb_exception except; TRY_CATCH (except, RETURN_MASK_ERROR) { value_fetch_lazy (val); } if (except.reason < 0) return 0; return 1; } So somewhere underneath this there is a disconnect about error handling, because this exception should have been caught here. I don't see anything obvious by just perusing the sources, so I'll have to dig in to see what could be happening. Keith