From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id mxMAOBqQS2CwZwAAWB0awg (envelope-from ) for ; Fri, 12 Mar 2021 11:00:26 -0500 Received: by simark.ca (Postfix, from userid 112) id CF47A1EF78; Fri, 12 Mar 2021 11:00:26 -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 196181E54D for ; Fri, 12 Mar 2021 11:00:26 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id EF0233857812; Fri, 12 Mar 2021 16:00:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF0233857812 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1615564825; bh=HpBK2tr/QpFcquuNgsH8dGNsnCCY4ksQeZ4yJMMPZPE=; h=To:Subject:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=cXTI9z+oj3FaEKOH5U+QEUdBpMDtwPJn0/mfldTr3uvVbYkHq+OWs/kxtx2lNf1fU f75eYVErJZAnzNp4JJ7xB5LBSLG96V1OB5Ct/avwLPT6iKrCdSjcgx/rNjZhpJ0zkh Z/x4fES2+UDIxxlCmsfKRE/NqFzgJquSc4mXBlgU= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 2E1C33857812 for ; Fri, 12 Mar 2021 16:00:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2E1C33857812 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-501-X837fdQyPgS7rgtP6z5D-w-1; Fri, 12 Mar 2021 11:00:19 -0500 X-MC-Unique: X837fdQyPgS7rgtP6z5D-w-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0BB8B93943; Fri, 12 Mar 2021 16:00:16 +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 3072A5C1D5; Fri, 12 Mar 2021 16:00:14 +0000 (UTC) To: Tom Tromey Subject: Re: Accessing pthread_key_create thread-specific data References: <874khg5xxn.fsf@oldenburg.str.redhat.com> <87wnuc2wqb.fsf@tromey.com> Date: Fri, 12 Mar 2021 17:00:27 +0100 In-Reply-To: <87wnuc2wqb.fsf@tromey.com> (Tom Tromey's message of "Fri, 12 Mar 2021 08:54:52 -0700") Message-ID: <87mtv84b1g.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.16 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 Cc: Florian Weimer via Gdb Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" * Tom Tromey: >>>>>> "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. Thanks for conforming. > 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? That's a good point. The data structures are not completely trivial to decode even if you have debuginfo symbols. I do not plan to work on that. I just had to make some changes on the glibc side, but I guess I just won't be able to test them. Thanks, Florian