Mouse
Mouse
> Do you have the ability to run this in a debugger? Alas, not really. :-( MacOS `lldb` and `dtrace` remain largely beyond my comprehension, and `gdb` doesn't really work...
> I guess the oqs test and the oqs provider are somehow linking against different versions of libcrypto. See for yourself: ```text $ otool -L /opt/local/lib/liboqs.dylib /opt/local/lib/liboqs.dylib: @rpath/liboqs.2.dylib (compatibility version...
`libcrypto.dylib` for OpenSSL-3.1.0 has no debug symbols, we're out of luck there. Binary install... I build `libcrypto.dylib` for OpenSSL-3.2.0-dev from source, therefore it has the appropriate debug symbols and such....
> So, my assumption is that the Python is picking up the 3.1.0 libcrypto version (no debug symbols) and then loading the oqsprovider which is picking up the 3.2.0-dev libcrypto...
I think we can close this. First, [this](https://github.com/openssl/openssl/issues/21023#issuecomment-1559625914) workaround tested OK, and second - it doesn't look like there's a way to "fix" or otherwise address it in the code.
BTW, speaking of `OPENSSL_init_crypto()` - looks like plenty of code in OpenSSL invokes this function. Here's a small excerpt: ```c . . . openssl/crypto/engine/eng_table.c 205: OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL); openssl/crypto/engine/eng_all.c 15: OPENSSL_init_crypto(OPENSSL_INIT_ENGINE_ALL_BUILTIN,...
> May I suggest to not close this issue . . . ? Sure. It looks like OpenSSL could do something to lower the probability of this issue rearing its...
> I don't think that oqsprovider and liboqs are ending up with different libcrypto versions. I think _python_ and oqsprovider are using different libcrypto versions, i.e. python is using the...
> marking as inactive, will be closed at the completion of 3.4 dev without further input "Inactive" means - user provided all the data he could collect, and the ball...
> It does reproduce without `stack`, using `cabal-install`. Here's a repo with the project described in the report: https://github.com/ulysses4ever/cabal-t8548-package-import-fail . Do a `cabal build all` on it: works with GHC...