libmysqlclient.so.18 segmentation fault on mysql_close_free_options

[4r1y4n]

I'm using apache2 version 2.4.7-1ubuntu4.5 with libmysqlclient18 version 5.7.5-m15-1ubuntu14.04 on Ubuntu 14.04
With moodle as php script apache exits with this log:

[Sun Sep 13 23:40:06.790779 2015] [core:notice] [pid 7829] AH00051: child pid 7832 exit signal Segmentation fault (11), possible coredump in /etc/apache2

I made apache to run only with one child process and attached to it using gdb & then tried to load moodle in browser and got segmentation fault :

Program received signal SIGSEGV, Segmentation fault.
0x00007f84d5632117 in mysql_close_free_options () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18

Here is Backtrace:

(gdb) backtrace
#0 0x00007f84d5632117 in mysql_close_free_options () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#1 0x00007f84d56324e6 in mysql_close () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#2 0x00007f84d51d3268 in php_mysqli_close () from /usr/lib/php5/20121212/mysqli.so
#3 0x00007f84d51d33b9 in zif_mysqli_close () from /usr/lib/php5/20121212/mysqli.so
#4 0x00007f84e373600b in dtrace_execute_internal () from /usr/lib/apache2/modules/libphp5.so
#5 0x00007f84e0c84476 in xdebug_execute_internal (current_execute_data=0x7f84e7a0a850, fci=0x0, return_value_used=0) at /build/buildd/xdebug-2.2.3/xdebug-2.2.3/xdebug.c:1551
#6 0x00007f84e37f6075 in ?? () from /usr/lib/apache2/modules/libphp5.so
#7 0x00007f84e376fda8 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
#8 0x00007f84e3735f09 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
#9 0x00007f84e0c83a7c in xdebug_execute_ex (execute_data=0x7f84e7a0a850) at /build/buildd/xdebug-2.2.3/xdebug-2.2.3/xdebug.c:1437
#10 0x00007f84e37f66c0 in ?? () from /usr/lib/apache2/modules/libphp5.so
#11 0x00007f84e376fda8 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
#12 0x00007f84e3735f09 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
#13 0x00007f84e0c83a7c in xdebug_execute_ex (execute_data=0x7f84e7a0a6c8) at /build/buildd/xdebug-2.2.3/xdebug-2.2.3/xdebug.c:1437
#14 0x00007f84e3738241 in zend_call_function () from /usr/lib/apache2/modules/libphp5.so
#15 0x00007f84e375d1e5 in zend_call_method () from /usr/lib/apache2/modules/libphp5.so
#16 0x00007f84e3768112 in zend_objects_destroy_object () from /usr/lib/apache2/modules/libphp5.so
#17 0x00007f84e376db05 in zend_objects_store_call_destructors () from /usr/lib/apache2/modules/libphp5.so
#18 0x00007f84e373653d in shutdown_destructors () from /usr/lib/apache2/modules/libphp5.so
#19 0x00007f84e3745fb4 in zend_call_destructors () from /usr/lib/apache2/modules/libphp5.so
#20 0x00007f84e36e6535 in php_request_shutdown () from /usr/lib/apache2/modules/libphp5.so
#21 0x00007f84e37f7c2f in ?? () from /usr/lib/apache2/modules/libphp5.so
#22 0x00007f84e78d5ba0 in ap_run_handler ()
#23 0x00007f84e78d60e9 in ap_invoke_handler ()
#24 0x00007f84e78eb6aa in ap_process_async_request ()
#25 0x00007f84e78eb984 in ap_process_request ()
#26 0x00007f84e78e8422 in ?? ()
#27 0x00007f84e78df1e0 in ap_run_process_connection ()
#28 0x00007f84e4117767 in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so
#29 0x00007f84e41179a6 in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so
#30 0x00007f84e411860e in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so
#31 0x00007f84e78bc8ae in ap_run_mpm ()
#32 0x00007f84e78b6046 in main ()

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Ubuntu does not ship libmysqlclient18 version 5.7.5-m15-1ubuntu14.04, so it seems to me that this is not a bug in Ubuntu. Instead you should report this bug with the party that provided that package to you.

Since this isn't a bug in Ubuntu, I'm marking this bug as Invalid in Ubuntu for now. If you can reproduce the bug with Apache, MySQL and PHP packages that ship with Ubuntu, or otherwise can demonstrate that this bug is in something that Ubuntu shipped rather than with an external source, then please provide exact steps to reproduce and then change the bug status back to New. Thanks!