From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1954 invoked by alias); 7 Aug 2007 11:49:44 -0000 Received: (qmail 1946 invoked by uid 22791); 7 Aug 2007 11:49:44 -0000 X-Spam-Check-By: sourceware.org Received: from mms3.broadcom.com (HELO MMS3.broadcom.com) (216.31.210.19) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 07 Aug 2007 11:49:42 +0000 Received: from [10.10.64.154] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.1)); Tue, 07 Aug 2007 04:49:30 -0700 X-Server-Uuid: 20144BB6-FB76-4F11-80B6-E6B2900CA0D7 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id E0E372AF; Tue, 7 Aug 2007 04:49:29 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id CE10E2AE for ; Tue, 7 Aug 2007 04:49:29 -0700 (PDT) Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com [10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id FNS38851; Tue, 7 Aug 2007 04:49:29 -0700 (PDT) Received: from NT-IRVA-0752.brcm.ad.broadcom.com ( nt-irva-0752.brcm.ad.broadcom.com [10.8.194.67]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id 6E1E369CA4 for ; Tue, 7 Aug 2007 04:49:29 -0700 (PDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: (Another) Segfault in varobj.c Date: Tue, 07 Aug 2007 11:49:00 -0000 Message-ID: From: "Robert Norton" To: gdb@sourceware.org X-WSS-ID: 6AA683C039C2939931-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-08/txt/msg00071.txt.bz2 Hi, I have encountered another crash seemingly originating in varobj.c. Whilst I've been able to work around the segfault I think there are some deeper rooted problems and I remembered from our previous conversation that the whole of this has been rewritten for 6.7. How self contained were these changes, i.e. would it be hard to back port them for our 6.6 based release? How risky would this be? Thanks, Robert