From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [patch][rfc] Allow GDB to search for the right libthread_db.so.1
Date: Tue, 25 Aug 2015 18:22:00 -0000 [thread overview]
Message-ID: <20150825182212.GB9494@host1.jankratochvil.net> (raw)
In-Reply-To: <CALoOobMh5payCOmGj_=0mSWNyua5ifih4Mc2iQ6kJBhL5tpiTw@mail.gmail.com>
On Tue, 25 Aug 2015 20:13:54 +0200, Paul Pluzhnikov wrote:
> We've had a lot of systems where installed /lib64/libthread_db was
> from glibc-2.7, while target binary was using glibc-2.3.6, and I am
> 99.99% sure that combination didn't work.
Pedro explained that glibc also does:
# $ grep -rn nptl_version nptl*
# nptl/ChangeLog.old:7461: * init.c (nptl_version): Add __attribute_used__ to nptl_version.
# nptl/nptl-init.c:68:static const char nptl_version[] __attribute_used__ = VERSION;
# nptl_db/td_ta_new.c:42: if (td_lookup (ps, SYM_nptl_version, &versaddr) != PS_OK)
# nptl_db/structs.def:53:DB_SYMBOL (nptl_version)
#
# So that alone makes a libthread_db.so for glibc 2.x refuse to work with glibc 2.y.
BTW the nptl_version check seems to predate the _thread_db_* symbols.
Thanks,
Jan
prev parent reply other threads:[~2015-08-25 18:22 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 20:39 Paul Pluzhnikov
2009-04-08 21:23 ` Thiago Jung Bauermann
2009-04-10 19:06 ` Paul Pluzhnikov
2009-04-16 17:56 ` Tom Tromey
2009-04-16 18:22 ` Eli Zaretskii
2009-04-17 19:13 ` Paul Pluzhnikov
2009-04-18 17:01 ` Eli Zaretskii
2009-04-19 14:59 ` Thiago Jung Bauermann
2009-04-19 18:03 ` Paul Pluzhnikov
2009-04-20 13:18 ` Daniel Jacobowitz
2009-04-20 16:47 ` Paul Pluzhnikov
2009-04-20 17:02 ` Daniel Jacobowitz
2009-04-20 17:20 ` Paul Pluzhnikov
2009-04-20 18:04 ` Daniel Jacobowitz
2009-04-20 19:09 ` Paul Pluzhnikov
2009-04-22 17:25 ` Daniel Jacobowitz
2009-04-23 1:10 ` Paul Pluzhnikov
2009-04-23 1:34 ` Tom Tromey
2009-04-23 6:28 ` Hui Zhu
2009-04-23 6:21 ` Hui Zhu
2009-04-23 7:01 ` Paul Pluzhnikov
2009-04-23 8:06 ` Hui Zhu
2009-04-23 11:32 ` Hui Zhu
2009-04-29 20:30 ` Paul Pluzhnikov
2009-04-30 5:38 ` Hui Zhu
2009-04-30 18:56 ` Joel Brobecker
2009-04-30 19:11 ` Paul Pluzhnikov
2009-04-30 22:12 ` Doug Evans
2009-04-30 23:18 ` Paul Pluzhnikov
2009-05-01 0:20 ` Paul Pluzhnikov
2009-05-11 13:13 ` Pedro Alves
2009-05-11 18:09 ` Paul Pluzhnikov
2009-05-11 21:09 ` Pedro Alves
2009-05-12 7:16 ` Hui Zhu
2009-05-12 16:42 ` Paul Pluzhnikov
2009-05-13 2:56 ` Hui Zhu
2009-05-13 3:29 ` Paul Pluzhnikov
2009-05-13 4:39 ` Hui Zhu
2009-05-15 14:37 ` Daniel Jacobowitz
2009-05-15 16:56 ` Paul Pluzhnikov
2009-05-01 7:21 ` Eli Zaretskii
2009-05-01 15:49 ` Paul Pluzhnikov
2009-05-01 16:49 ` Daniel Jacobowitz
2009-05-01 17:02 ` Paul Pluzhnikov
2009-05-01 17:11 ` Daniel Jacobowitz
2009-05-01 17:17 ` Pedro Alves
2009-05-01 18:53 ` Doug Evans
2009-05-04 0:07 ` Hui Zhu
2009-05-04 3:31 ` Paul Pluzhnikov
2009-05-05 2:54 ` Hui Zhu
2009-05-05 3:38 ` Joel Brobecker
2009-05-05 11:42 ` Hui Zhu
2009-05-11 11:34 ` Pedro Alves
2009-05-11 12:24 ` Joel Brobecker
2009-04-20 17:37 ` Paul Pluzhnikov
2009-04-20 18:46 ` Eli Zaretskii
2015-08-25 18:01 ` Jan Kratochvil
2015-08-25 18:14 ` Paul Pluzhnikov
2015-08-25 18:22 ` Jan Kratochvil [this message]
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=20150825182212.GB9494@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=ppluzhnikov@google.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