This is the mail archive of the
mailing list for the GDB project.
Re: RFA: properly handle the GIL
- From: Daniel Jacobowitz <drow at false dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 20 Nov 2008 20:49:07 -0500
- Subject: Re: RFA: properly handle the GIL
- References: <email@example.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
This looks OK. Is this a recursive lock? That is, do we have to
worry about GDB -> Python -> GDB -> Python taking the lock twice?