From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5066 invoked by alias); 24 Oct 2014 14:58:34 -0000 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 Received: (qmail 5055 invoked by uid 89); 24 Oct 2014 14:58:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 24 Oct 2014 14:58:33 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s9OEwP77004558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 24 Oct 2014 10:58:25 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s9OEwMfE019669; Fri, 24 Oct 2014 10:58:23 -0400 Message-ID: <544A690E.3030405@redhat.com> Date: Fri, 24 Oct 2014 14:58:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Ulrich Weigand , Martin Galvan CC: gdb-patches@sourceware.org, dje@google.com, Eli Zaretskii Subject: Re: [PATCH] Python API: Add gdb.is_in_prologue and gdb.is_in_epilogue. References: <201410231757.s9NHvX3r026780@d06av02.portsmouth.uk.ibm.com> In-Reply-To: <201410231757.s9NHvX3r026780@d06av02.portsmouth.uk.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-10/txt/msg00644.txt.bz2 On 10/23/2014 06:57 PM, Ulrich Weigand wrote: > The in_prologue routine is likewise only still uses under certain rather > rare circumstances; in fact it might even today be possible to simply > remove it. Yes, I think so, see: https://sourceware.org/ml/gdb-patches/2014-10/msg00643.html Thanks, Pedro Alves