From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id NovAG/BlS2DUYwAAWB0awg (envelope-from ) for ; Fri, 12 Mar 2021 08:00:32 -0500 Received: by simark.ca (Postfix, from userid 112) id 657531EF78; Fri, 12 Mar 2021 08:00:32 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 669631E793 for ; Fri, 12 Mar 2021 08:00:31 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id ACBA9398B8A6; Fri, 12 Mar 2021 13:00:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ACBA9398B8A6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1615554030; bh=3FNNqn/968yvU/r+FozIYNDCP9CUQbDab9LSrMU/fMU=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=aQD4545PmblRCOF6elVROzQaTRieeJO19AC08ge2rY9gLTFmBxz+PxnXlGt9Saexq 7WcCFbz+lR3R4rsFsL8yQ8fT1o0/nCy8jq9PVWUC8TGu5k2kpnS+7UusIU9Gcju7AA PcD48eWml0+Uc8j7NuxK453lt2ekTE6cAc9dF+EI= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id B3105398B8A4 for ; Fri, 12 Mar 2021 13:00:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B3105398B8A4 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-290-v1s9HDrIMC-SUvEawcLVUQ-1; Fri, 12 Mar 2021 08:00:26 -0500 X-MC-Unique: v1s9HDrIMC-SUvEawcLVUQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5D6281015C84 for ; Fri, 12 Mar 2021 13:00:25 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-112-77.ams2.redhat.com [10.36.112.77]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C439F2B16D for ; Fri, 12 Mar 2021 13:00:24 +0000 (UTC) To: gdb@sourceware.org Subject: Accessing pthread_key_create thread-specific data Date: Fri, 12 Mar 2021 14:00:36 +0100 Message-ID: <874khg5xxn.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain 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: , From: Florian Weimer via Gdb Reply-To: Florian Weimer Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" We have some functionality in libthread_db in glibc that provides access to pthread_key_create thread-specific data (aka pthread_setspecific and pthread_getspecific). I would like to write a GDB test for this functionality, but I can't find how GDB exposes this data in the UI. Is this just dead code? The symbols we provide are td_ta_tsd_iter and td_thr_tsd. Thanks, Florian