This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch][rfc] Allow GDB to search for the right libthread_db.so.1


On Fri, May 1, 2009 at 02:55, Joel Brobecker <brobecker@adacore.com> wrote:
> Just my 2 cents, from an outsider's point of view:
>
>> 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.
>
> From my naive perspective (never really had a need for this feature),
> it seems better to check the path before checking the path that was
> used by the inferior. ?Otherwise, if the local host has a library
> at the same location but that's different from the library used
> by the inferior, we wouldn't be able to force the debugger to use
> a different library, would we?
>
>> 2. Allow libthread_db_search_path contain files as well as directories.
> [...]
>> 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.
>
> This one seems much less important, if at all, to me, especially if
> it is unlikely that libthread_db might have a different name. And
> even in this case, it's easy to create a symbolic link in a user
> area, and update the path to point to that directory.

If we can let user create a slink here,  User can create slink to
right lib with themselves.  Maybe they don't need set
libthread_db_search_path then.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]