Bug #80920 MySQL Connector Causes Segfault
Submitted: 31 Mar 2016 9:03 Modified: 1 Apr 2016 9:29
Reporter: Ross Beer Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:5.7.11 OS:CentOS (7)
Assigned to: CPU Architecture:Any

[31 Mar 2016 9:03] Ross Beer 
Description:
ODBC connector causes a segfault when connecting to server:

Program terminated with signal 11, Segmentation fault.
#0  mysql_get_character_set_info (mysql=0x7f5964091fa8, csinfo=0x7f59505ef260) at /export/home/pb2/build/sb_0-17781605-1454370718.35/mysql-5.7.11/libmysql/libmysql.c:1056
#0  mysql_get_character_set_info (mysql=0x7f5964091fa8, csinfo=0x7f59505ef260) at /export/home/pb2/build/sb_0-17781605-1454370718.35/mysql-5.7.11/libmysql/libmysql.c:1056
No locals.
#1  0x00007f59dc05d40d in myodbc_do_connect (dbc=dbc@entry=0x7f5964091fa0, ds=ds@entry=0x7f59640491c0) at /usr/src/debug/mysql-connector-odbc-5.3.6-src/driver/connect.c:261
        my_charset = {number = 58, state = 0, csname = 0x1a <Address 0x1a out of bounds>, name = 0x0, comment = 0x3a <Address 0x3a out of bounds>, dir = 0x0, mbminlen = 3758291164, mbmaxlen = 32601}
        rc = 0
        mysql = 0x7f5964091fa8
        flags = 131072
        opt_ssl_verify_server_cert = 4294967295
        on = 1 '\001'
        max_long = 18446744073709551615

The issue happens when using either type of driver be that ANSI or UNICODE.

This is happening on multiple servers and happens at random times.

How to repeat:
The issue happens at least once a day at random times
[31 Mar 2016 10:38] Chiranjeevi Battula 
Hello Ross Beer,

Thank you for the bug report.
Could you please provide repeatable test case and more information like MySQL version, Connector / ODBC version, driver manager and used build version(default build or modified build) to confirm this issue at our end?
This is most likely duplicate of Bug #62007.

Thanks,
Chiranjeevi.
[31 Mar 2016 13:38] Ross Beer 
I am unable to reproduce on the fly, the crash happens randomly.

I have regressed to MySQL repository 5.6 where the issue doesn't happen.
[1 Apr 2016 9:29] Chiranjeevi Battula 
Hello Ross Beer,

Thank you for your feedback.
I could not repeat this issue at my end with the provided information. 
If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Thanks,
Chiranjeevi.