From: James Cownie <jcownie@etnus.com>
To: gdb@sources.redhat.com
Subject: Re: GDB support for thread-local storage
Date: Tue, 25 Jun 2002 09:11:00 -0000 [thread overview]
Message-ID: <17Msup-0Qw-00@etnus.com> (raw)
In-Reply-To: Message from Daniel Jacobowitz <drow@mvista.com> of "Tue, 25 Jun 2002 11:55:55 EDT." <20020625155555.GA18083@branoic.them.org>
> You'll never get them to document interface changes in pthreads'
> internal data structures. You're welcome to try if you like pain
> more than I do. The only layer the glibc folks support for
> accessing this data is thread_db.
I'm not sugggesting that they document it, rather that they provide a
version symbol which tells you which version of the pthreads code you
have, and then name libthread_db with a name which includes the
version number.
All I'm after is that one can tell from a debugger which version of
the pthread library one is looking at and then deduce which
libthread_db.so to dlopen.
Something as trivial as
static volatile int __pthread_version_number = 123;
somwehere would probably do.
The documentation requirement would be
The static symbol __pthread_version_number gives the version number
of the pthread library to allow a debugger to locate the appropriate
version of libthread_db.
and that's it. It doesn't change...
Thought they need to remember to change the version number when they
make changes which affect libthread_db.
-- Jim
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com
next prev parent reply other threads:[~2002-06-25 16:11 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1024952640.13693.ezmlm@sources.redhat.com>
2002-06-25 1:48 ` James Cownie
2002-06-25 8:05 ` Daniel Jacobowitz
2002-06-25 8:31 ` James Cownie
2002-06-25 8:42 ` Daniel Jacobowitz
2002-06-25 8:53 ` James Cownie
2002-06-25 8:56 ` Daniel Jacobowitz
2002-06-25 9:11 ` James Cownie [this message]
2002-06-25 9:29 ` Daniel Jacobowitz
2002-06-25 10:44 ` Andrew Cagney
2002-06-25 10:02 ` Daniel Jacobowitz
2002-06-26 12:45 ` Jim Blandy
2002-06-26 19:31 ` Andrew Cagney
2002-06-26 21:57 ` Jim Blandy
2002-06-27 8:13 ` Andrew Cagney
2002-08-19 9:05 ` Daniel Jacobowitz
2003-02-17 18:07 [maint] The GDB maintenance process Daniel Jacobowitz
[not found] ` <drow@mvista.com>
2003-02-17 18:58 ` Kevin Buettner
2003-10-10 15:30 ` Unambiguously specifying source locations Daniel Jacobowitz
2003-10-10 15:44 ` David Ayers
2003-10-10 15:46 ` Daniel Jacobowitz
2003-10-11 2:21 ` Felix Lee
2003-02-17 21:01 ` [maint] The GDB maintenance process Elena Zannoni
2003-02-19 1:49 ` Daniel Jacobowitz
2003-02-19 2:26 ` Joel Brobecker
2003-02-19 15:43 ` Andrew Cagney
2003-02-19 16:29 ` Daniel Jacobowitz
2003-02-19 22:04 ` Andrew Cagney
2003-02-19 13:24 ` Daniel Berlin
2003-02-19 15:51 ` Andrew Cagney
2003-02-19 14:50 ` Andrew Cagney
2003-02-19 17:33 ` David Carlton
2003-02-19 17:57 ` Kevin Buettner
2003-02-19 18:56 ` Andrew Cagney
2003-02-19 20:39 ` Christopher Faylor
2003-02-19 23:17 ` Jason Molenda
2003-02-20 1:53 ` Christopher Faylor
2003-02-19 19:35 ` David Carlton
2003-02-20 18:32 ` Richard Earnshaw
2003-02-22 0:53 ` Andrew Cagney
2003-02-19 15:12 ` Andrew Cagney
2003-02-19 15:21 ` Daniel Jacobowitz
2003-02-19 16:24 ` Andrew Cagney
2003-02-19 18:36 ` Christopher Faylor
2003-02-19 23:36 ` Jason Molenda
2003-02-19 23:52 ` Andrew Cagney
2003-02-19 23:59 ` Jason Molenda
2003-02-20 0:16 ` Elena Zannoni
2003-02-20 0:21 ` Andrew Cagney
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 4:28 ` Andrew Cagney
2003-02-19 3:49 ` Jim Blandy
2003-02-19 16:14 ` Andrew Cagney
2003-02-19 16:31 ` Daniel Jacobowitz
2003-02-19 2:24 ` Jim Blandy
2003-02-19 16:33 ` Andrew Cagney
2003-02-19 22:24 ` Jim Blandy
2003-02-19 22:39 ` Christopher Faylor
2003-02-19 22:53 ` Andrew Cagney
2003-02-19 23:53 ` Elena Zannoni
2003-02-20 1:27 ` Andrew Cagney
2003-02-20 2:48 ` Andrew Cagney
2003-02-21 23:43 ` Andrew Cagney
2003-02-21 23:57 ` Andrew Cagney
2003-02-19 6:05 ` David Carlton
2003-02-23 23:26 ` Mark Kettenis
2003-02-24 7:18 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 9:00 GDB support for thread-local storage Jim Blandy
2002-06-19 10:08 ` Daniel Berlin
2002-06-19 12:20 ` Jim Blandy
2002-06-19 13:12 ` Daniel Berlin
2002-06-19 13:40 ` Jim Blandy
2002-06-20 18:35 ` Andrew Cagney
2002-06-20 18:48 ` Daniel Jacobowitz
2002-06-21 10:18 ` Andrew Cagney
2002-06-21 10:32 ` Daniel Jacobowitz
2002-06-21 13:08 ` Jim Blandy
2002-06-21 13:18 ` Daniel Jacobowitz
2002-06-21 13:54 ` Jim Blandy
2002-06-21 14:03 ` Daniel Jacobowitz
2002-06-21 14:46 ` Andrew Cagney
2002-06-21 14:55 ` Daniel Jacobowitz
2002-06-21 15:31 ` Andrew Cagney
2002-06-21 22:59 ` Daniel Jacobowitz
2002-06-22 8:22 ` Andrew Cagney
2002-06-24 7:53 ` Daniel Jacobowitz
2002-06-21 16:14 ` Jim Blandy
2002-06-21 22:57 ` Daniel Jacobowitz
2002-06-26 12:37 ` Jim Blandy
2002-06-21 13:20 ` Daniel Jacobowitz
2002-06-21 15:37 ` Jim Blandy
2002-06-21 23:00 ` Daniel Jacobowitz
2002-06-21 12:34 ` Jim Blandy
2002-06-21 12:49 ` Jim Blandy
2002-06-21 18:10 ` Jim Blandy
2002-06-21 20:24 ` Andrew Cagney
2002-06-21 21:09 ` Jim Blandy
2002-06-22 8:31 ` Andrew Cagney
2002-06-21 15:04 ` Andrew Cagney
2002-06-21 15:41 ` Jim Blandy
2002-06-21 15:59 ` Andrew Cagney
2002-06-21 16:08 ` Jim Blandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17Msup-0Qw-00@etnus.com \
--to=jcownie@etnus.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).