Re: Please add code to pick up SOLIB_SEARCH_PATH env var.

[Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>]

  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