Cross solib support; continued

[Orjan Friberg <orjan dot friberg at axis dot com>]

A couple of more questions regarding support for cross solibs:

1. I need some way to make gdb not care about the path to a solib, i.e.
ignore "/lib" when searching for "/lib/libc.so.6".  This is because the
directory where the unstripped solibs reside isn't called "lib".  In
effect, I'm grabbing the unstripped solibs from the compiler's include
directories instead of from (a copy of) the target's file system (since
those solibs are stripped).  Nope, can't have unstripped solibs on the
target.

That is, I would like a solib that is now searched for in
solib-absolute-prefix to be searched for in solib-search-path instead. 
Would it make sense to add such a command, like solib-ignore-path?  (I'd
be happy to make it happen.)  In effect, it would make all solibs to be
searched for in solib-search-path by file name only, and
solib-absolute-path would have no effect.

2. With a work-around for the directory problem above, when I start the
program under the gdbserver I get hold of it in _start in ld.so.1, but
the symbols for ld.so.1 aren't loaded.  More specifically, I can't "list
_start" and backtrace gives me "#0  0x1aaadc34 in ?? ()".  I assume this
is because gdb hasn't had a chance to put a breakpoint in ld.so.1 that
would make it know about the loading of it.  Chicken-egg problem, but
not really a problem; few developers will ever have to debug glibc's
startup routines.  I just wanted to check I understand the limitations
correctly.  (The stuff in ld.so.1 is loaded by the time I get to main,
so that part works.)

-- 
Orjan Friberg
Axis Communications AB