Introspecting the call stack is possible, if somewhat ugly, using the backtrace 
and backtrace_symbols functions (on macOS/iOS.) But all you get is a list of PC 
and stack addresses, or function names. I don’t know how you’d go from those to 
an NSBundle object. On cursory inspection I didn’t see any NSBundle methods for 
finding out where in memory the associated code is loaded.


Cocoa-dev mailing list (

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)

Help/Unsubscribe/Update your Subscription:

This email sent to

Reply via email to