Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: <Paul_Koning@Dell.com>
To: <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Python 3 support, part 1 (non-testsuite part)
Date: Tue, 13 Nov 2012 19:56:00 -0000	[thread overview]
Message-ID: <C75A84166056C94F84D238A44AF9F6AD29E6BE@AUSX10MPC103.AMER.DELL.COM> (raw)
In-Reply-To: <87mwyl70hu.fsf@fleche.redhat.com>


On Nov 13, 2012, at 2:42 PM, Tom Tromey wrote:

>>>>>> "Paul" ==   <Paul_Koning@Dell.com> 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

Does that mean that a make cleanup done before the try-catch is not in effect within the try-catch?

	paul


  reply	other threads:[~2012-11-13 19:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 16:06 Paul_Koning
2012-11-12 20:43 ` Tom Tromey
2012-11-12 21:37   ` Paul_Koning
2012-11-13 18:53     ` Tom Tromey
2012-11-13 19:02       ` Paul_Koning
2012-11-13 19:12         ` Tom Tromey
2012-11-13 19:26           ` Paul_Koning
2012-11-13 19:43             ` Tom Tromey
2012-11-13 19:56               ` Paul_Koning [this message]
2012-11-13 20:24                 ` Tom Tromey
2012-11-14 16:03                   ` Paul_Koning
2012-11-19 16:49                     ` Tom Tromey
2012-12-11 20:22                       ` Paul_Koning
2012-12-11 20:37                         ` Eli Zaretskii
2012-12-11 21:24                         ` Tom Tromey
2012-12-12 17:00                           ` Paul_Koning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C75A84166056C94F84D238A44AF9F6AD29E6BE@AUSX10MPC103.AMER.DELL.COM \
    --to=paul_koning@dell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox