From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 758 invoked by alias); 2 Mar 2009 15:24:48 -0000 Received: (qmail 426 invoked by uid 22791); 2 Mar 2009 15:24:45 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Mar 2009 15:24:33 +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 n22FOUqg030158 for ; Mon, 2 Mar 2009 10:24:30 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n22FOXOT022853 for ; Mon, 2 Mar 2009 10:24:33 -0500 Received: from opsy.redhat.com (vpn-12-5.rdu.redhat.com [10.11.12.5]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n22FOVD8032449; Mon, 2 Mar 2009 10:24:31 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 626A78880CE; Mon, 2 Mar 2009 08:24:24 -0700 (MST) To: Aleksandar Ristovski Cc: gdb-patches@sources.redhat.com Subject: Re: [patch] Fix SIGSEGV in gdb when printing ctor of non-virtual class References: <48DD1C8A.7030206@qnx.com> From: Tom Tromey Reply-To: tromey@redhat.com Date: Mon, 02 Mar 2009 15:24:00 -0000 In-Reply-To: (Aleksandar Ristovski's message of "Mon\, 02 Mar 2009 09\:28\:01 -0500") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-03/txt/msg00011.txt.bz2 >>>>> "Aleksandar" == Aleksandar Ristovski writes: Aleksandar> An old patch. Gdb still SIGSEGV on this testcase, but I Aleksandar> haven't got any replies. Aleksandar> + /* Constructors of non-virtual classes will not have block. */ This seems weird. Is this a gcc bug or something? Should this somehow be fixed elsewhere? I don't know. Aleksandar> + release_value (v); I don't think you want release_value here. You can just drop the value, it will automatically be freed later. Tom