Post not yet marked as solved
We have two dynamic libraries (with different names) that bring in duplicate symbols. What we are seeing is, that when a dyld_stub is generated in the assembly code, the wrong dylibs implementation is called. Is there a way to prevent this (ie. some way to disable lazy symbol binding)?
Post not yet marked as solved
Our application is hanging on launch. Looking at the callstack we have a call to CFBundleGetFunctionPointerForName which eventually causes another call to CFBundleGetFunctionPointerForName. We hang with the following subset of the callstack:
2550 CFBundleGetFunctionPointerForName	(in CoreFoundation) + 39	[0x7fff2c0bdd4a]
		+																																																																																									 2550 _CFBundleLoadExecutableAndReturnError	(in CoreFoundation) + 316	[0x7fff2c0f5e0f]
		+																																																																																										 2550 _pthread_mutex_firstfit_lock_slow	(in libsystem_pthread.dylib) + 211	[0x7fff6dc89218]
		+																																																																																											 2550 _pthread_mutex_firstfit_lock_wait	(in libsystem_pthread.dylib) + 81	[0x7fff6dc8b31d]
		+																																																																																												 2550 __psynch_mutexwait	(in libsystem_kernel.dylib) + 10	[0x7fff6dbc21be]
Do we need to refactor our code to prevent recursive calls or is this a bug in 10.16?
I want my application to run the same inside and outside of XCode. The issue is DYLD_LIBRARY_PATH is causing the wrong libraries to be found when running my executable. Is there a way to clear it? My attempts to try and clear it only appended to the process environment variable. Also, how exactly is it determined? I am not explicitily setting it. I am using CMake. Thank you,Kris Berg
krisberg.