From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29130 invoked by alias); 8 Jul 2009 22:14:33 -0000 Received: (qmail 29117 invoked by uid 22791); 8 Jul 2009 22:14:32 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_24,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 08 Jul 2009 22:14:23 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n68MEM9i022775; Wed, 8 Jul 2009 18:14:22 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n68MELjO005035; Wed, 8 Jul 2009 18:14:21 -0400 Received: from stone.twiddle.home (vpn-9-141.rdu.redhat.com [10.11.9.141]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n68MEKnT003634; Wed, 8 Jul 2009 18:14:20 -0400 Message-ID: <4A551A3C.7020606@redhat.com> Date: Wed, 08 Jul 2009 22:14:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2 MIME-Version: 1.0 To: Larry Evans CC: gcc@gcc.gnu.org Subject: Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol "__extension__"', error msg References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00149.txt.bz2 On 07/08/2009 03:11 PM, Larry Evans wrote: > It would be much easier if gdb understood __extension__. Is there a way? In this case, no. It's protecting a statement expression, which gdb will never be able to parse. A better project for helping debug gcc would be to convert all macros that use statement expressions into proper inline functions. Which would then be emitted as out-of-line functions by gcc's -fkeep-inlines flag, which would yield something that's callable from within gdb. r~