From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: properly handle the GIL
Date: Fri, 21 Nov 2008 19:07:00 -0000 [thread overview]
Message-ID: <20081121014907.GA19748@caradoc.them.org> (raw)
In-Reply-To: <m3od09eu4g.fsf@fleche.redhat.com>
On Thu, Nov 20, 2008 at 06:38:07PM -0700, Tom Tromey wrote:
> This patch changes gdb to only acquire the GIL before running Python
> code. This is now a general rule for hacking on the Python
> integration: if the call chain originates in gdb, and enters Python,
> then the GIL must first be acquired. Currently only the "python"
> command is affected, but there are more instances on the python
> branch.
This looks OK. Is this a recursive lock? That is, do we have to
worry about GDB -> Python -> GDB -> Python taking the lock twice?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-21 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 18:46 Tom Tromey
2008-11-21 19:07 ` Daniel Jacobowitz [this message]
2008-11-21 19:13 ` Tom Tromey
2008-11-21 19:25 ` Tom Tromey
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=20081121014907.GA19748@caradoc.them.org \
--to=drow@false.org \
--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