Hi, I have a legacy application that uses OpenSSL 1.1.1 statically and I am getting segfault error at connection with UnixODBC and MSSQL. We have used this versions: Operating System: NAME="Oracle Linux Server" VERSION="9.6"
unixODBC: 2.3.11
Compiler: g++ (GCC) 11.5.0 20240719
ODBC Driver: Microsoft ODBC Driver 18 for SQL Server (18.5)
Database: Microsoft SQL Server 2022 The application is composed by app and shared libraries. We reproduced the structure in the example available at:https://github.com/fgarbin/odbc_launcher_cpp When I use sample program with openssl 1.1.1 I have the segfault error, if I use openssl 3.0.13 the error go away. The core dump stack, when the error occur, is showed below: Stack trace of thread 874956: #0 0x00007f6a6fb45daa EC_GROUP_order_bits (/media/data/github/fgarbin/odbc_launcher_cpp/libodb> #1 0x00007f6a6fb3db7e ec_bits (/media/data/github/fgarbin/odbc_launcher_cpp/libodbc_launcher.s> #2 0x00007f6a6df736ad engine_unlocked_init (libcrypto.so.3 + 0x1736ad) #3 0x00007f6a6df7676b ENGINE_init (libcrypto.so.3 + 0x17676b) #4 0x00007f6a6dfb87b1 int_ctx_new (libcrypto.so.3 + 0x1b87b1) #5 0x00007f6a6f15a963 SSL_CTX_new_ex (libssl.so.3 + 0x40963) #6 0x00007f6a6e967267 n/a (libmsodbcsql-18.5.so.1.1 + 0x167267) #7 0x00007f6a6e961e72 n/a (libmsodbcsql-18.5.so.1.1 + 0x161e72) #8 0x00007f6a6e96273b n/a (libmsodbcsql-18.5.so.1.1 + 0x16273b) #9 0x00007f6a6e92a96f n/a (libmsodbcsql-18.5.so.1.1 + 0x12a96f) #10 0x00007f6a6e927c8d n/a (libmsodbcsql-18.5.so.1.1 + 0x127c8d) #11 0x00007f6a6e9287fa n/a (libmsodbcsql-18.5.so.1.1 + 0x1287fa) #12 0x00007f6a6e92909c n/a (libmsodbcsql-18.5.so.1.1 + 0x12909c) #13 0x00007f6a6e897676 n/a (libmsodbcsql-18.5.so.1.1 + 0x97676) #14 0x00007f6a6e899193 SQLConnectW (libmsodbcsql-18.5.so.1.1 + 0x99193) #15 0x00007f6a6ee10ca0 SQLConnect (libodbc.so + 0x10ca0) #16 0x00007f6a6fdfa09d db_connect (/media/data/github/fgarbin/odbc_launcher_cpp/libdbinterface.> #17 0x00007f6a6faaf693 connect_and_run_sql (/media/data/github/fgarbin/odbc_launcher_cpp/libodb> #18 0x00000000004024dc main (app_odbc_launcher + 0x24dc)
Is there some way to solve or get a workaround to this issue ? Thanks |