From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7446 invoked by alias); 20 Sep 2010 09:32:31 -0000 Received: (qmail 7435 invoked by uid 22791); 20 Sep 2010 09:32:31 -0000 X-SWARE-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Sep 2010 09:32:26 +0000 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o8K9WOW5013304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 20 Sep 2010 05:32:24 -0400 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o8K9WNUM005690; Mon, 20 Sep 2010 05:32:23 -0400 Message-ID: <4C972A26.6040505@redhat.com> Date: Mon, 20 Sep 2010 10:15:00 -0000 From: Phil Muldoon User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100907 Fedora/3.0.7-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.7 MIME-Version: 1.0 To: Paul Bolle CC: gdb-patches@sourceware.org Subject: Re: [PATCH] [RFC] python: gdb.Type: strip typedefs past pointers too References: <1284753356.21566.10.camel@localhost.localdomain> In-Reply-To: <1284753356.21566.10.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2010-09/txt/msg00337.txt.bz2 On 09/17/2010 08:55 PM, Paul Bolle wrote: > 0) gdb.Type.strip_typedefs() stops stripping types if it encounters a > type that is a pointer to a typedef: > > 1) I drafted a patch (pasted below this message) that works around this > limitation: I think the current behaviour is correct. And we are limited in what we can change in these situations. Would it break existing scripts? Still, I like your patch. Would you consider submitting it so that it can be turned on (off by default) via keyword? (i.e. a recurse=True keyword). That would allow us to preserve the existing functionality, but allow the user an API friendly way for this alternate recursive behaviour? Cheers, Phil