From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Release the GIL while running a gdb command or expression
Date: Tue, 29 Jan 2019 13:02:00 -0000 [thread overview]
Message-ID: <87lg33vcqm.fsf@tromey.com> (raw)
In-Reply-To: <8736sg4z50.fsf@tromey.com> (Tom Tromey's message of "Sun, 04 Nov 2018 08:54:03 -0700")
>>>>> "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.
Tom
prev parent reply other threads:[~2019-01-29 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 20:23 Tom Tromey
2018-10-12 14:52 ` Phil Muldoon
2018-10-12 16:49 ` Pedro Alves
2018-10-12 16:51 ` Pedro Alves
2018-10-16 12:48 ` Tom Tromey
2018-10-16 14:50 ` Pedro Alves
2018-10-12 16:56 ` Pedro Alves
2018-10-16 13:05 ` Tom Tromey
2018-10-16 14:51 ` Pedro Alves
2018-10-16 21:39 ` Tom Tromey
2018-10-16 21:45 ` Tom Tromey
2018-10-24 18:08 ` Pedro Alves
2018-10-25 12:46 ` Phil Muldoon
2018-11-04 15:54 ` Tom Tromey
2019-01-29 13:02 ` Tom Tromey [this message]
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=87lg33vcqm.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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