On Monday, 23 May 2022 at 05:10:35 UTC+1 Gonzalo wrote:
On 22/5/22 21:08, Gonzalo Garramuño wrote:
> strace is helpful in that it shows all DSOs being loaded. However, it
> does not seem to list them in a tree view fashion (or in a proper
> order either), which is what I would need. I am looking for the
> equivalent of Windows' DLLs Dependency Walker (depends.exe).
Okay, I found what I needed. lddtree (from app-misc/pax-utils). That
lists DSOs in a tree fashion.
Hi Gonzalo,
Glad you found that - I knew it existed, but couldn't actually remember what it was called!
Did it show anything useful?
Might be interesting to see what it did show, too.
As an aside - I'm not really understanding what you are doing - it sounds to me like you are linking a number of SO files into your app, and providing them in a private libs folder, specific to your app? (To which end you are overwriting LD_LIBRARY_PATH to find your "local" libs.)
Would it not be cleaner to simply static link the "local" libs and then allow the default library load path to load all the other "system" libs that are needed?
As I say, I'm not at all clear on what you are doing, so I was puzzled...
As an aside, I'm not all that comfortable with the possibility that your app might be loading two different versions of the TLS lib here, that just seems... scary, frankly.
I think I'd be more comfortable if there was only one!
