From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26676 invoked by alias); 13 Nov 2012 19:43:09 -0000 Received: (qmail 26667 invoked by uid 22791); 13 Nov 2012 19:43:08 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS 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; Tue, 13 Nov 2012 19:42:55 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qADJgs6m017224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 13 Nov 2012 14:42:54 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id qADJgreP009567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 13 Nov 2012 14:42:53 -0500 From: Tom Tromey To: Cc: Subject: Re: [PATCH] Python 3 support, part 1 (non-testsuite part) References: <87mwyma6xi.fsf@fleche.redhat.com> <87390d8hdf.fsf@fleche.redhat.com> <87y5i571xi.fsf@fleche.redhat.com> Date: Tue, 13 Nov 2012 19:43:00 -0000 In-Reply-To: (Paul Koning's message of "Tue, 13 Nov 2012 19:25:52 +0000") Message-ID: <87mwyl70hu.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-11/txt/msg00334.txt.bz2 >>>>> "Paul" == writes: Paul> What I meant is that if I set the PyBuffer_Release as the cleanup Paul> function, it will be called if the handle_exception machinery gets an Paul> exception and returns out from under me. Right? Yeah, if you make the cleanup inside the try-catch. But then you have to explicitly call do_cleanups or discard_cleanups as well. Tom