Re:RE: DETERMINE LOAD PATH OF LINKED FRAMEWORK AT RUNTIME
Re:RE: DETERMINE LOAD PATH OF LINKED FRAMEWORK AT RUNTIME
- Subject: Re:RE: DETERMINE LOAD PATH OF LINKED FRAMEWORK AT RUNTIME
- From: "email@hidden" <email@hidden>
- Date: Thu, 06 Jun 2013 15:51:57 -0400
Testing
From: email@hidden
Date: Wednesday, June 5, 2013
To: Graham Cox <email@hidden>
Subject: Re: Determine load path of linked framework at runtime
>>On 5 Jun 2013, at 3:59 PM, Graham Cox wrote:
>>> Hi all,
>>>
>>> Is there a way to discover the load path of a framework at runtime?
>>>
>>> I have an odd situation where a framework which is bundled within my app is being overridden by an older copy on a user's machine. They've tried looking in all the usual /Frameworks locations and performed a search but to no avail. If there's some way to log the actual load path used that would reveal the problem immediately, I'm thinking.
>>
>>For a one-off, they can try running the program with the DYLD_PRINT_LIBRARIES environment variable set (see the dyld(1) man page).
>>
>>You can also query the dynamic linker's information about a library at run time using dladdr().
>>
>>
>>
>>_______________________________________________
>>
>>Cocoa-dev mailing list (email@hidden)
>>
>>Please do not post admin requests or moderator comments to the list.
>>Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>>
>>Help/Unsubscribe/Update your Subscription:
>>
>>This email sent to email@hidden
>>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden