Project Home
Project Home
Source Code
Source Code
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - DL_DEBUG: (8 Items)
   
DL_DEBUG  
DL_DEBUG is nice but I want to know where it loaded the shared object from, the exact path.  Any way to do that?

- Mario
Re: DL_DEBUG  
ldd?

I don't see why we shouldn't change DL_DEBUG though to dump the fullpath

Mario Charest wrote:
> DL_DEBUG is nice but I want to know where it loaded the shared object from, the exact path.  Any way to do that?
> 
> - Mario
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post18021
> 

-- 
cburgess@qnx.com
RE: DL_DEBUG  

> -----Original Message-----
> From: Colin Burgess [mailto:community-noreply@qnx.com]
> Sent: December-05-08 11:34 AM
> To: general-toolchain
> Subject: Re: DL_DEBUG
> 
> ldd?
> 


Not sure what you mean?

> I don't see why we shouldn't change DL_DEBUG though to dump the
> fullpath

Would be nice. I had a rogue shared object hiding somewhere in LD_LIBRARY_PATH, was nasty to find, these things like to 
hide.

> 
> Mario Charest wrote:
> > DL_DEBUG is nice but I want to know where it loaded the shared object
> from, the exact path.  Any way to do that?
> >
> > - Mario
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post18021
> >
> 
> --
> cburgess@qnx.com
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post18023
> 
Re: DL_DEBUG  
ldd <your binary>
gives you exactly would be loaded assuming you run it using same LD_LIRBARY_PATH

Mario Charest wrote:
> 
>> -----Original Message-----
>> From: Colin Burgess [mailto:community-noreply@qnx.com]
>> Sent: December-05-08 11:34 AM
>> To: general-toolchain
>> Subject: Re: DL_DEBUG
>>
>> ldd?
>>
> 
> 
> Not sure what you mean?
> 
>> I don't see why we shouldn't change DL_DEBUG though to dump the
>> fullpath
> 
> Would be nice. I had a rogue shared object hiding somewhere in LD_LIBRARY_PATH, was nasty to find, these things like 
to hide.
> 
>> Mario Charest wrote:
>>> DL_DEBUG is nice but I want to know where it loaded the shared object
>> from, the exact path.  Any way to do that?
>>> - Mario
>>>
>>> _______________________________________________
>>> General
>>> http://community.qnx.com/sf/go/post18021
>>>
>> --
>> cburgess@qnx.com
>>
>> _______________________________________________
>> General
>> http://community.qnx.com/sf/go/post18023
>>
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post18027
> 
RE: DL_DEBUG  
> ldd <your binary>
> gives you exactly would be loaded assuming you run it using same
> LD_LIRBARY_PATH

Lovely, thanks 

> Mario Charest wrote:
> >
> >> -----Original Message-----
> >> From: Colin Burgess [mailto:community-noreply@qnx.com]
> >> Sent: December-05-08 11:34 AM
> >> To: general-toolchain
> >> Subject: Re: DL_DEBUG
> >>
> >> ldd?
> >>
> >
> >
> > Not sure what you mean?
> >
> >> I don't see why we shouldn't change DL_DEBUG though to dump the
> >> fullpath
> >
> > Would be nice. I had a rogue shared object hiding somewhere in
> LD_LIBRARY_PATH, was nasty to find, these things like to hide.
> >
> >> Mario Charest wrote:
> >>> DL_DEBUG is nice but I want to know where it loaded the shared
> object
> >> from, the exact path.  Any way to do that?
> >>> - Mario
> >>>
> >>> _______________________________________________
> >>> General
> >>> http://community.qnx.com/sf/go/post18021
> >>>
> >> --
> >> cburgess@qnx.com
> >>
> >> _______________________________________________
> >> General
> >> http://community.qnx.com/sf/go/post18023
> >>
> >
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post18027
> >
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post18029
> 
RE: DL_DEBUG  
The Utilities Reference will include an entry for ldd in the next
release.


Steve Reid (stever@qnx.com)
Technical Editor
QNX Software Systems 
 
Re: RE: DL_DEBUG  
Having DL_DEBUG provide the full path would still be really handy for those of us who use dlopen for which ldd is not a 
lot of use (though I suppose we can still use 'which -s').
Re: DL_DEBUG  
I agree, and will make a PR.

Colin

Roger Maclean wrote:
> Having DL_DEBUG provide the full path would still be really handy for those of us who use dlopen for which ldd is not 
a lot of use (though I suppose we can still use 'which -s').
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post18033
> 

-- 
cburgess@qnx.com