Re: libthread_db thread handles

[Ulrich Drepper <drepper at redhat dot com>]

-----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 <thread_db.h>. 
> 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-----