From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56891 invoked by alias); 29 Jan 2019 13:02:10 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 56879 invoked by uid 89); 29 Jan 2019 13:02:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=HX-HELO:sk:gateway X-HELO: gateway34.websitewelcome.com Received: from gateway34.websitewelcome.com (HELO gateway34.websitewelcome.com) (192.185.148.204) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 29 Jan 2019 13:02:05 +0000 Received: from cm10.websitewelcome.com (cm10.websitewelcome.com [100.42.49.4]) by gateway34.websitewelcome.com (Postfix) with ESMTP id A14D2AFBEC for ; Tue, 29 Jan 2019 07:02:01 -0600 (CST) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id oT1dgOwZD2PzOoT1dgxopr; Tue, 29 Jan 2019 07:02:01 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=WGGj5QzVkSSsc5ALPehX+CckJ6CIYlAPEIyxF/TvAZE=; b=ZNRRFLeYTmYMDeCsfto2BOyN+S Q0U71Vi/AUfqUUhFAsMyb/iZ+GgvQD3z3VyrEPdRr0QUd23GgADsKA0G1nO56H1tbfttTcqqGPbhL FM4juXCcD6vXZa4sqJHI409Lv; Received: from herd.wildebeest.org ([80.127.118.209]:58254 helo=bapiya) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1goT1c-000MtJ-UC; Tue, 29 Jan 2019 07:02:01 -0600 From: Tom Tromey To: Tom Tromey Cc: Pedro Alves , gdb-patches@sourceware.org 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> Date: Tue, 29 Jan 2019 13:02:00 -0000 In-Reply-To: <8736sg4z50.fsf@tromey.com> (Tom Tromey's message of "Sun, 04 Nov 2018 08:54:03 -0700") Message-ID: <87lg33vcqm.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2019-01/txt/msg00605.txt.bz2 >>>>> "Tom" == Tom Tromey 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