From: Yoshinori Toshima <yoshinori.toshima@oracle.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: Please add code to pick up SOLIB_SEARCH_PATH env var.
Date: Thu, 16 Dec 2010 13:23:00 -0000 [thread overview]
Message-ID: <4D0A128D.40201@oracle.com> (raw)
In-Reply-To: <20101216112614.fa2rmsu5eso0o0ok@webmail.u-strasbg.fr>
Hello Pierre,
Thank you for your comment.
Currently, single path element works. It is rare to have same libraries
with
same name in different directories.
To support multiple path elements, we need to check solib_search_path
variable use in solib.c again. If it can have comma separated path
elements,
then we can check each environment variable and join valid elements with
colon and set it to solib_search_path.
> Did you try 'gdb -ex "set solib-search-patch ..."' ?
No I haven't. I'll check it.
Regards,
Yoshinori
(10/12/16 19:26), Pierre Muller wrote:
> I was wondering if your patch
> would work if the environment variable had
> several entries, like;
> SOLIB_SEARCH_PATH=/myprefix/lib:/myprefix/lib64
>
> Does access return 0 if you
> give it the whole evironment variable, or should
> you test the coponents one by one?
>
> Pierre Muller
>
>> Yoshinori Toshima <yoshinori.toshima@oracle.com> a écrit :
>>
>> Hello,
>>
>> I have a small enhancement request for GDB to make it easier to
>> use when debugging core file from other systems which have
>> different libraries.
>>
>> Description:
>> When debugging a core file from released product, it is convenient
>> to have gdb use shared libraries in a directory which contains the
>> libraries and executable taken from the system which caused the
>> crash. It is possible to perform this by gdb command "set
>> solib-search-path <path>". This means some commands are required
>> after starting gdb. If we can set solib-search-path at gdb startup,
>> it is easier to use. This is useful when we use GDB programmatically.
>>
>> HP-UX port of GDB has this feature via env var GDB_SHLIB_PATH.
>> GDB does not have the feature yet, though it mentions SOLIB_SEARCH_PATH
>> in solib.c.
>>
>> I changed solib.c to pick up SOLIB_SEARCH_PATH at startup and set
>> it to solib_search_path in solib.c initialization. It worked as
>> expected.
>>
>> Attached solib-patch.diff is based on solib.c in gdb 7.2.
>>
>> ChangeLog entry:
>> 2010-12-16 Yoshinori Toshima <yoshinori.toshima@oracle.com>
>>
>> * solib.c: Pick up SOLIB_SEARCH_PATH env var to set solib-search-path at
>> startup.
>>
>> Regards,
>> Yoshinori Toshima
>>
>
>
>
>
next prev parent reply other threads:[~2010-12-16 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 9:29 Yoshinori Toshima
2010-12-16 10:26 ` Pierre Muller
2010-12-16 13:23 ` Yoshinori Toshima [this message]
2010-12-16 14:23 ` Yoshinori Toshima
2010-12-16 13:07 ` Pedro Alves
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=4D0A128D.40201@oracle.com \
--to=yoshinori.toshima@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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