From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27234 invoked by alias); 14 Jan 2003 23:08:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 27163 invoked from network); 14 Jan 2003 23:08:27 -0000 Received: from unknown (HELO myware.akkadia.org) (24.221.190.179) by 209.249.29.67 with SMTP; 14 Jan 2003 23:08:27 -0000 Received: from redhat.com (myware.akkadia.org [192.168.7.70]) (authenticated bits=0) by myware.akkadia.org (8.12.5/8.12.5) with ESMTP id h0EN8KYA002756; Tue, 14 Jan 2003 15:08:21 -0800 Message-ID: <3E249864.2060600@redhat.com> Date: Tue, 14 Jan 2003 23:08:00 -0000 From: Ulrich Drepper Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030111 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz CC: Michael Snyder , Roland McGrath , gdb@sources.redhat.com Subject: Re: libthread_db thread handles References: <20030110204624.GA32002@nevyn.them.org> <86wulbc29o.fsf@elgar.kettenis.dyndns.org> <20030113214916.GA18517@nevyn.them.org> <3E235404.45568034@redhat.com> <20030114002758.GA30705@nevyn.them.org> <3E24901B.4841796E@redhat.com> <20030114224641.GA18618@nevyn.them.org> In-Reply-To: <20030114224641.GA18618@nevyn.them.org> X-Enigmail-Version: 0.72.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00244.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel Jacobowitz wrote: > First of all, libthread_db doesn't necessarily create the > td_thrhandle_t; they're allocated by the caller of libthread_db, for > map_id2thr and map_lwp2thr. The iterators create them and then throw > them away, of course. ...which is why you cannot reply on the addresses of these objects to have any relevance. This is why I mentioned it. > td_thrhandle_t is opaque; it is documented as opaque in . > I don't want to look at th_unique. Can I rely on the fact that the contents > of a td_thrhandle_t are stable and can be re-used if I save the > td_thrhandle_t? In the current implementation this is the case but I don't want to commit to this unless you can show me there are big benefits. It would help if you could describe what functions you see being used often and in which contexts. There are things in the libthread_db implementation which can be changed without breaking the ABI. We just need to know how you use the library. - -- - --------------. ,-. 444 Castro Street Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA Red Hat `--' drepper at redhat.com `--------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+JJhk2ijCOnn/RHQRAivlAJ0V9WNF9X4Dus63bliLW8M42exPJwCgn/wa yMXOoHldlHIHSL4Lq+rjIqA= =ySWh -----END PGP SIGNATURE-----