From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Hui Zhu <teawater@gmail.com>
Cc: tromey@redhat.com, Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches ml <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch][rfc] Allow GDB to search for the right libthread_db.so.1
Date: Wed, 29 Apr 2009 20:30:00 -0000 [thread overview]
Message-ID: <8ac60eac0904291330m78b43c47p1cc9b8379e31e923@mail.gmail.com> (raw)
In-Reply-To: <daef60380904230432l7f49d44dw17437e208b35cb9f@mail.gmail.com>
On Thu, Apr 23, 2009 at 4:32 AM, Hui Zhu <teawater@gmail.com> wrote:
> In function thread_db_load, I suggest try_thread_db_load with
> libthread_db_search_path first.
> Cause I think if user set a directory, he must want it be loaded.
Hui made two suggestions:
1. If libthread_db_search_path is set, use it *before* trying to load
libthread_db from the same directory where libpthread was loaded in the
inferior.
2. Allow libthread_db_search_path contain files as well as directories.
Both are (IMHO) reasonable, though I don't particularly like either.
Implementing 1) will cause a bit of searching, because most of the time
the libthread_db which "parallels" libpthread is the right one (at least
for us), and the search is really there mostly for static executables
(which are somewhat rare here).
Implementing 2) "clouds" the meaning of libthread_db_search_path somewhat,
and it is quite unlikely (though certainlyh possible) that libthread_db
will be called anything other than libthread_db.so.1 on Linux.
Comments?
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-04-29 20:30 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 [this message]
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
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=8ac60eac0904291330m78b43c47p1cc9b8379e31e923@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
--cc=tromey@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