Bug #16394: libmysqlclient20 5.7.28-0ubuntu0.18.04.4 causes segmentation fault

• Status: Third Party's Issue
• Assignee: -
• Target version: -
• ruby -v: ruby 2.3.6p384 (2017-12-14 revision 61254) [x86_64-linux]
• Backport: 2.5: UNKNOWN, 2.6: UNKNOWN

[duthmanek (Tim Dithmer)]

OS: Ubuntu 18.04

Update from libmysqlclient20 to 5.7.28-0ubuntu0.18.04.4 causes segmentation fault while using mysql- and mysql2-gem.

Stacktrace is in attached log

[duthmanek (Tim Dithmer)]

duthmanek (Tim Dithmer) wrote:

OS: Ubuntu 18.04

Update from libmysqlclient20 to 5.7.28-0ubuntu0.18.04.4 causes segmentation fault while using mysql- and mysql2-gem.

Stacktrace is in attached log

Gem Versions:
mysql (2.9.1)
mysql2 (0.5.2)

[jeremyevans0 (Jeremy Evans)]

• Status changed from Open to Third Party's Issue

This happens while loading the mysql2 gem:

/opt/chef/embedded/lib/libruby.so.2.3(sigsegv+0x3e) [0x7f4ad936d22e] signal.c:890
/lib/x86_64-linux-gnu/libc.so.6 [0x7f4ad8e58f20]
/lib/x86_64-linux-gnu/libc.so.6 [0x7f4ad8f83d76]
/opt/chef/embedded/lib/libcrypto.so.1.0.0(getrn+0x89) [0x7f4ad6ad6fc9]
/opt/chef/embedded/lib/libcrypto.so.1.0.0(lh_insert+0xd8) [0x7f4ad6ad7338]
/opt/chef/embedded/lib/libcrypto.so.1.0.0(OBJ_NAME_add+0x6f) [0x7f4ad6a3197f]
/usr/lib/x86_64-linux-gnu/libssl.so.1.1 [0x7f4ad0e8be5e]
/lib/x86_64-linux-gnu/libpthread.so.0(__pthread_once_slow+0xb7) [0x7f4ad8c0a827]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1(CRYPTO_THREAD_run_once+0x9) [0x7f4ad0b6c8f9]
/usr/lib/x86_64-linux-gnu/libssl.so.1.1(OPENSSL_init_ssl+0x8b) [0x7f4ad0e8c07b]
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 [0x7f4ad1140224]
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20(mysql_server_init+0x67) [0x7f4ad1105c27]
/opt/chef/embedded/lib/ruby/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/mysql2.so(init_mysql2_client+0xc) [0x7f4ad16a6d0c] client.c:1392
/opt/chef/embedded/lib/ruby/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/mysql2.so(Init_mysql2+0x76) [0x7f4ad16aaa86] mysql2_ext.c:11
/opt/chef/embedded/lib/libruby.so.2.3(dln_load+0x110) [0x7f4ad923b400] dln.c:1355

It appears to be a problem either in libmysqlclient or OpenSSL, or their interaction. As the crash happens inside OpenSSL_init_ssl, my guess would be it is OpenSSL related, and you may want to report it to them. You would probably want to get a stacktrace with debugging symbols before reporting it to OpenSSL.