gdb/633: fully qualified pathnames in solib_map_sections() and remote debugging

[jorma dot laaksonen at hut dot fi]

>Number:         633
>Category:       gdb
>Synopsis:       fully qualified pathnames in solib_map_sections() and remote debugging
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 06 03:08:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     jorma.laaksonen@hut.fi
>Release:        gdb-5.2
>Organization:
>Environment:
--host=i686-pc-linux-gnu --target=arm-linux
>Description:
When debugging remotely an application that runs
in another type of platform, solib_map_sections() of solib.c gets called with fully qualified pathnames
that are correct in the target system but not necessarily
in the host system.  Or, the host system's solib versions
are of incorrect file format for the cross-target gdb.

When such a solib doesn't exist in host's filesystem,
a loop of errors like

> Error while mapping shared library sections:
> /usr/lib/libxxx.so.1: No such file or directory.

is entered.
>How-To-Repeat:

>Fix:
Add a variable that specifies search path for solibs
while debugging remotely ???
>Release-Note:
>Audit-Trail:
>Unformatted: