This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2] Release the GIL while running a gdb command or expression
- From: Pedro Alves <palves at redhat dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 29 Jan 2019 16:37:40 +0000
- Subject: Re: [PATCH v2] Release the GIL while running a gdb command or expression
- References: <20181010202233.17985-1-tom@tromey.com> <6c7d1b6d-2d7a-dcaf-8d20-615bfb474af9@redhat.com> <871s8qcab9.fsf@tromey.com> <4aa9c215-9b86-40f9-37e9-d96121e80736@redhat.com> <87woqhbmh6.fsf@tromey.com> <87sh15bm71.fsf@tromey.com> <8b981b27-1e15-31d8-0342-492700468ecf@redhat.com> <8736sg4z50.fsf@tromey.com> <87lg33vcqm.fsf@tromey.com>
On 01/29/2019 01:01 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>
> Tom> The main thread can't run any Python code at all. If it does run Python
> Tom> code, then Python might release the GIL. And, when dealing with thread
> Tom> primitives like mutexes or whatnot, it certainly will. However, if the
> Tom> main thread does release the GIL, then that invalidates the test --
> Tom> since we are trying to test that the GIL is released under ordinary
> Tom> circumstances.
>
> Tom> I'm back to not seeing a way to test this.
>
> It's been a while since we discussed this. I still don't know of a way
> to test it. I think that the bug fix still makes sense in the absence
> of a test, though.
Fine with me to put this in without a test.
Thanks,
Pedro Alves