On Fri, Nov 19, 2021 at 05:36:24PM +1100, Grahame Grieve wrote:
> It's very definitely something active that OSX is doing. Here's an OSX
> error generated:
>
> System Integrity Protection: enabled
>
> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>
> Exception Type: EXC_CRASH (SIGABRT)
> Exception Codes: 0x0000000000000000, 0x0000000000000000
> Exception Note: EXC_CORPSE_NOTIFY
>
> Application Specific Information:
> abort() called
> Invalid dylib load. Clients should not load the unversioned libcrypto
> dylib as it does not have a stable ABI.
Well, I think that's evidence of confusion about which "libcrypto" to
load. It sure seems that you're trying to load the default system
libcrypto, not the one in the application bundle.
You should probably arrange to "salt" the names of the libssl and
libcrypto libraries used by your application, so that there can't
be any confusion with the platform's libssl and libcrypto.
May also need to do something to avoid symbol name collisions, but I
haven't looked into how that works on Darwin, so can't offer specific
advice.
--
Viktor.
