search

open-webrtc-toolkit / owt-client-native

Open WebRTC Toolkit client SDK for native Windows/Linux/iOS applications.
https://01.org/open-webrtc-toolkit
Apache License 2.0
389 stars 181 forks source link

Runtime error EXC_BAD_ACCESS in ssl_lib.cc #559

Closed dilldilldill closed 2 years ago

dilldilldill commented 2 years ago

After compiling socket.io-client-cpp (with the help of socket.io-client-cpp-ios-static) linking the libsioclient_tls.a file into my project was not enough, as Xcode was still complaining about undefined symbols (_SSL_ctrl, _SSL_CTX_ctrl and _CONF_modules_unload). So I also linked OpenSSL's libcrypto.a and libssl.a file which eventually allowed me to successfully compile my project.

But now I am stuck with a runtime error which occurs as soon as I try to make a connection using OWT.

EXC_BAD_ACCESS (code=257, address=0x3f3910043fd)

#1  0x0000000100f046c8 in ::SSL_CTX_new(const SSL_METHOD *) at /../../third_party/boringssl/src/ssl/ssl_lib.cc:605

error: memory read failed for 0x7391004200
dilldilldill commented 2 years ago

I downloaded CS_WebRTC_Client_SDK_iOS.v5.0.zip which contains precompiled OWT and WebRTC framework. After I linked those into my project the undefined OpenSSL symbols disappeared and I was able to build my project without linking OpenSSL. Now everything seems to be working fine.