RE: [dsdp-dd-dev] Remote Debugging commit

["Marc Khouzam" <marc.khouzam@xxxxxxxxxxxx>]

Great!
With info shared (before setting ssyroot or solib-search-path),
I got the library information.  However, there was no path
besides the library name, and yet sysroot did not work to find it.

This may have to do with Daniel's concern of the "target only supplying
relative path".  Or it may be our OS that has another quirk.

I will take this off list, since it is a problem with our internal things.

As for DSDP/DD, I'm hoping to have as much "automatic discovery" for those
paths, so I'll see if solib-search-path or sysroot is better.

Thanks for your help.

marc

-----Original Message-----
From: dsdp-dd-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx]On Behalf Of Frederic RISS
Sent: Thursday, March 13, 2008 12:13 PM
To: Device Debugging developer discussions
Subject: Re: [dsdp-dd-dev] Remote Debugging commit



Le jeudi 13 mars 2008 à 12:02 -0400, Daniel Jacobowitz a écrit :
> On Thu, Mar 13, 2008 at 11:54:49AM -0400, Marc Khouzam wrote:
> > Is there a way for me to know the full path GDB is looking for?
> 
> Yes - it should be displayed in "info shared".  I'm not sure what will
> happen if the target supplies only relative paths though.

This might be self-evident, but...
This will only work if you unset sysroot and solib-search-path so that
GDB doesn't find a corresponding library. IIRC, if GDB finds a solib it
will display its full name, not the one requested by the target_so_ops.

_______________________________________________
dsdp-dd-dev mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev