From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: fix atexit.register
Date: Thu, 20 Sep 2012 20:46:00 -0000 [thread overview]
Message-ID: <87y5k4tocb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <874nn5d5ur.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 10 Sep 2012 13:40:12 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> * NEWS: Update.
Tom> * python/python.c (finalize_python): New function.
Tom> (_initialize_python): Make a final cleanup.
Tom> * gdb.python/python.exp: Test atexit.register.
I'm checking this in.
Tom
next prev parent reply other threads:[~2012-09-20 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 15:43 Tom Tromey
2012-09-06 16:13 ` Eli Zaretskii
2012-09-10 19:40 ` Tom Tromey
2012-09-10 19:52 ` Eli Zaretskii
2012-09-20 20:46 ` Tom Tromey [this message]
2012-09-21 7:05 ` Regression for build --without-python [Re: RFC: fix atexit.register] Jan Kratochvil
2012-11-29 19:13 ` [commit] Fix !HAVE_THREAD Python build error (Re: RFC: fix atexit.register) Ulrich Weigand
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=87y5k4tocb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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