From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gateway32.websitewelcome.com (gateway32.websitewelcome.com [192.185.145.111]) by sourceware.org (Postfix) with ESMTPS id 61871386F429 for ; Fri, 12 Mar 2021 15:54:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 61871386F429 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=tom@tromey.com Received: from cm10.websitewelcome.com (cm10.websitewelcome.com [100.42.49.4]) by gateway32.websitewelcome.com (Postfix) with ESMTP id 9AFAC14699A for ; Fri, 12 Mar 2021 09:54:53 -0600 (CST) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id Kk7plsofCkscSKk7ploWBB; Fri, 12 Mar 2021 09:54:53 -0600 X-Authority-Reason: nr=8 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=KfjZwAcQs6GZy7M2GXX0Tpm9W2kj1fLIck09mCxKVmg=; b=wkugxnTSPgXoKW2LrUuSmFVfz5 G7yY3/7HKi6tV/5zPVNwEPybWF31bBkMUKikTTjnbrjzLNSmDD44XFFWdbzIx8ILVchsenEfrF4z9 732f8RV2T9HResZQuDr7iWTwR; Received: from 71-211-137-228.hlrn.qwest.net ([71.211.137.228]:37664 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1lKk7p-000x3C-9F; Fri, 12 Mar 2021 08:54:53 -0700 From: Tom Tromey To: Florian Weimer via Gdb Cc: Florian Weimer Subject: Re: Accessing pthread_key_create thread-specific data References: <874khg5xxn.fsf@oldenburg.str.redhat.com> X-Attribution: Tom Date: Fri, 12 Mar 2021 08:54:52 -0700 In-Reply-To: <874khg5xxn.fsf@oldenburg.str.redhat.com> (Florian Weimer via Gdb's message of "Fri, 12 Mar 2021 14:00:36 +0100") Message-ID: <87wnuc2wqb.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 71.211.137.228 X-Source-L: No X-Exim-ID: 1lKk7p-000x3C-9F X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 71-211-137-228.hlrn.qwest.net (murgatroyd) [71.211.137.228]:37664 X-Source-Auth: tom+tromey.com X-Email-Count: 1 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3020.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, JMQ_SPF_NEUTRAL, RCVD_IN_ABUSEAT, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_NEUTRAL, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2021 15:54:56 -0000 >>>>> "Florian" == Florian Weimer via Gdb writes: Florian> We have some functionality in libthread_db in glibc that provides access Florian> to pthread_key_create thread-specific data (aka pthread_setspecific and Florian> pthread_getspecific). I would like to write a GDB test for this Florian> functionality, but I can't find how GDB exposes this data in the UI. Is Florian> this just dead code? As far as I know, these aren't used and I think have never been used. I'm not sure how I would go about exposing this to users. The most natural way might be to intercept calls to pthread_*specific. Maybe a couple of new convenience functions would be good though, and less magical. I guess this would primarily be useful for core file debugging? Assuming inferior calls to pthread_*specific already work -- I haven't tried. thanks, Tom